ABUSE.MOM
THREAT REPORT

IP Threat Report
18.224.135.250

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 19:16:55
First seen: 2026-05-06 03:00:06
Last seen: 2026-05-06 03:00:06
140

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
18.224.135.250
Type
Hosting
Country
🇺🇸 United States
City
Dublin
ISP
Amazon.com, Inc.
Organization
AWS EC2 (us-east-2)
Autonomous System
AS16509 Amazon.com, Inc.
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Σ = 140
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-06 03:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 5 (+100), 404 ratio 40-60% (+15)
2026-05-06 03:00:06
Last malicious request observed
Total score reached: 140/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon.com, Inc.
AS16509 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 18.224.135.250 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

🤖 User-Agent Anomaly Defense

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

🔎 Directory Scan Defense

IP 18.224.135.250 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

09

Blacklist Status (DNSBL)

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

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
zen.spamhaus.org
✓ Clean
truncate.gbudb.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

18.224.135.250 has been assigned a threat score of 140/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

User-Agent AnomalyPath Enumeration

📊 Threat Analysis

Threat intelligence analysis has linked 18.224.135.250 to malicious activity originating from Dublin, United States, operating on the network of Amazon.com, Inc.. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 130 blocked IPs in our database, making it a significant source of malicious traffic. At 140/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 United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)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 Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 DNS Sinkholing for Malware Defense

DNS sinkholing redirects queries for known malicious domains to controlled IP addresses. This technique blocks malware communication, prevents data exfiltration, and identifies compromised internal hosts attempting to contact command-and-control servers.

🔍 Check Any IP Address

Share this report: