ABUSE.MOM
THREAT REPORT

IP Threat Report
18.220.212.113

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 08:46:28
First seen: 2026-09-22 00:05:05
Last seen: 2026-09-27 01:39:15
145

⛔ Verdict: BLOCK

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

BOT_UABURSTREFERERUA_CHANGED
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 13/2sAbnormally fast request rate — automated scanning+35
Burst 14/10sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
UA bot: pythonKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 145
03

Observed Activity

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

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

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

04

Timeline

2026-09-22 00:05:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 13/2s (+35), Burst 14/10s (+35), Foreign referer (+10)
2026-09-27 01:39:15
Last malicious request observed
Total score reached: 145/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

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

We have detected 1328 malicious IPs from this autonomous system.

View all IPs from AS16509 →
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 18.220.212.113.

🤖 User-Agent Anomaly Defense

IP 18.220.212.113 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
b.barracudacentral.org
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

18.220.212.113 has been assigned a threat score of 145/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:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

18.220.212.113 is registered in Columbus, United States, operating on the network of Amazon.com, Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 5-day observation window, we recorded 129 hostile requests from this IP — roughly 25.8 per day on average. 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 (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 36,230 malicious IPs originating from United States, positioning it as a major contributor to global threat activity. A score of 145/100 places this address in the top tier of severity. Block and investigate any historical connections.

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: AS16509

3.26.255.172 (308)3.26.98.5 (308)35.180.172.183 (298)3.129.218.216 (288)18.191.74.68 (288)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Phishing Infrastructure Analysis

Modern phishing operations use sophisticated infrastructure including lookalike domains, valid TLS certificates, and evasion techniques like cloaking and geofencing. Analyzing this infrastructure reveals campaigns before they reach their targets.

🔍 Check Any IP Address

Share this report: