ABUSE.MOM
THREAT REPORT

IP Threat Report
3.236.53.220

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-06 01:24:12
First seen: 2026-08-31 21:08:57
Last seen: 2026-09-06 01:02:48
135

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
3.236.53.220
Type
Hosting
Country
🇺🇸 United States
City
Ashburn
ISP
Amazon Technologies Inc.
Organization
AWS EC2 (us-east-1)
Autonomous System
AS14618 Amazon.com, Inc.
Hit Count
139
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 135
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-08-31 21:08:57
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger strong hits: 14 (+100), Probe 302→404 (+20)
2026-09-06 01:02:48
Last malicious request observed
Total score reached: 135/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Amazon Technologies Inc.
AS14618 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 3.236.53.220 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 3.236.53.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

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

07

Neighbors in 3.236.53.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

3.236.53.220 has been assigned a threat score of 135/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 Enumeration

📊 Threat Analysis

Network traffic from 3.236.53.220, located in Ashburn, United States, operating on the network of Amazon Technologies Inc., has been classified as malicious by our automated threat scoring engine. During its 5-day observation window, we recorded 139 hostile requests from this IP — roughly 27.8 per day on average. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 202 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 135/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.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS14618

18.209.46.145 (288)13.219.225.47 (288)13.219.221.213 (288)98.86.112.239 (263)34.224.58.198 (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.

💡 Critical Infrastructure Targeting

Attacks on power grids, water systems, and transportation networks have moved from theoretical to practical threats. Industrial control systems often lack modern security features, making them vulnerable to both targeted and opportunistic attacks.

🔍 Check Any IP Address

Share this report: