ABUSE.MOM
THREAT REPORT

IP Threat Report
167.71.56.87

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-15 15:53:09
First seen: 2026-09-14 20:44:18
Last seen: 2026-09-15 15:04:44
273

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404REFERER
01

Geolocation & Classification

IP Address
167.71.56.87
Type
Hosting
Country
🇩🇪 Germany
City
Frankfurt am Main
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
15
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 104/10sAbnormally fast request rate — automated scanning+35
Burst 104/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 60Medium-risk: admin panels, config files+60
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
Σ = 273
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-14 20:44:18
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 104/10s (+35), Burst 104/2s (+35)
2026-09-15 15:04:44
Last malicious request observed
Total score reached: 273/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇩🇪 Germany
06

Recommendations

Actions taken & recommended

  • IP 167.71.56.87 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 167.71.56.87 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Flood / DDoS Mitigation

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

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.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

167.71.56.87 has been assigned a threat score of 273/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

Threat intelligence analysis has linked 167.71.56.87 to malicious activity originating from Frankfurt am Main, Germany, operating on the network of DigitalOcean, LLC. The address has been under observation since its initial detection. During its 1-day observation window, we recorded 15 hostile requests from this IP — roughly 15 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 (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. At 273/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 Germany

104.248.17.30 (208)206.189.60.220 (205)46.101.115.233 (205)68.183.218.41 (205)68.183.64.6 (205)View all →

🏢 Same network: AS14061

142.93.195.73 (275)152.42.236.252 (273)204.48.19.26 (268)157.230.45.147 (265)152.42.180.126 (263)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.

💡 WebSocket Security Considerations

WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.

🔍 Check Any IP Address

Share this report: