ABUSE.MOM
THREAT REPORT

IP Threat Report
209.97.180.8

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 10:47:03
First seen: 2026-03-01 21:00:05
Last seen: 2026-05-24 10:21:58
198

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404
01

Geolocation & Classification

IP Address
209.97.180.8
Type
Hosting
Country
🇬🇧 United Kingdom
City
Slough
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
542
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 15/10sAbnormally fast request rate — automated scanning+35
Burst 16/10sAbnormally fast request rate — automated scanning+35
Burst 7/2sAbnormally fast request rate — automated scanning+35
Burst: 12 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 13 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 26 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 7 req / 2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
POST requests presentBehavioral anomaly detected by automated analysis+8
POST seenBehavioral anomaly detected by automated analysis+8
Σ = 536
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-03-01 21:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 15/10s (+35), Burst 16/10s (+35)
2026-05-24 10:21:58
Last malicious request observed
Total score reached: 198/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇬🇧 United Kingdom
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

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

🌊 Traffic Flood Defense

IP 209.97.180.8 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

209.97.180.8 has been assigned a threat score of 198/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 EnumerationRequest Flooding

📊 Threat Analysis

The address 209.97.180.8 originates from Slough, United Kingdom, operating on the network of DigitalOcean, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 83 days, this IP generated 542 malicious requests, averaging approximately 6.5 requests per day. 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 Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 103 malicious IPs originating from United Kingdom, positioning it as a significant contributor to global threat activity. A score of 198/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 Kingdom

104.28.208.60 (340)104.28.240.60 (340)91.230.225.3 (305)45.86.203.224 (305)45.86.203.35 (305)View all →

🏢 Same network: AS14061

129.212.237.216 (308)168.144.34.140 (295)170.64.203.182 (280)161.35.89.38 (273)64.226.94.117 (273)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.

💡 Emerging Threats from AI-Powered Attacks

Artificial intelligence enables more convincing phishing content, faster vulnerability discovery, and adaptive attack strategies that learn from defensive responses. AI-generated social engineering and automated exploit development represent growing threats.

🔍 Check Any IP Address

Share this report: