ABUSE.MOM
THREAT REPORT

IP Threat Report
96.0.0.119

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:54:02
First seen: 2026-05-05 21:00:05
Last seen: 2026-05-30 07:51:41
130

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 130/100. Total malicious requests observed: 994.

DANGER_PATHMETHODRATIO_404REDIRECT_PROBEREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
96.0.0.119
Type
Hosting
Country
🇦🇺 Australia
City
Sydney
ISP
Amazon.com
Organization
AWS EC2 (ap-southeast-2)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
994
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger medium hits: 5Medium-risk: admin panels, config files+50
Danger medium hits: 9Medium-risk: admin panels, config files+60
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Foreign refererReferer from unrelated external domain+10
POST requests presentBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 323
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-05-05 21:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 2 (+20), Danger medium hits: 4 (+40)
2026-05-30 07:51:41
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon.com
AS16509 · 🇦🇺 Australia
06

Recommendations

Actions taken & recommended

  • IP 96.0.0.119 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 96.0.0.119: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🤖 User-Agent Anomaly Defense

IP 96.0.0.119 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl.dronebl.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

96.0.0.119 has been assigned a threat score of 130/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 96.0.0.119 to malicious activity originating from Sydney, Australia, operating on the network of Amazon.com. The address has been under observation since its initial detection. The address has been active for 24 days in our monitoring system, producing 994 flagged requests at a rate of ~41.4/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 101 flagged addresses, Australia represents a significant presence in our threat database. At 130/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇦🇺 Top threats from Australia

20.42.209.0 (280)170.64.203.182 (280)20.213.152.227 (280)20.5.72.178 (280)4.197.33.200 (280)View all →

🏢 Same network: AS16509

15.220.152.241 (320)18.219.106.176 (315)15.220.169.114 (280)108.136.131.13 (265)54.206.58.169 (263)View all →
12

Security Intelligence

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 Backup and Recovery Against Ransomware

Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.

🔍 Check Any IP Address

Share this report: