ABUSE.MOM
THREAT REPORT

IP Threat Report
213.160.71.86

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 22:57:19
First seen: 2026-09-09 12:45:17
Last seen: 2026-09-13 01:14:04
130

⛔ Verdict: BLOCK

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

DANGER_PATH
01

Geolocation & Classification

IP Address
213.160.71.86
Type
Hosting
Country
🇩🇪 Germany
City
Aachen
ISP
Hosting.de GmbH
Organization
.net
Autonomous System
AS12574 Hosting.de GmbH
Hit Count
123
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Σ = 130
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-09-09 12:45:17
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 3 (+30), Danger strong hits: 4 (+100)
2026-09-13 01:14:04
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Hosting.de GmbH
AS12574 · 🇩🇪 Germany
06

Recommendations

Actions taken & recommended

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

⚙️ Defensive Recommendations

Block 213.160.71.86 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

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

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

10

Threat Analysis

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

📊 Threat Analysis

IP address 213.160.71.86 has been traced to Aachen, Germany, operating on the network of Hosting.de GmbH. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 3-day observation window, we recorded 123 hostile requests from this IP — roughly 41 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. Germany currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 130/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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

15.220.152.241 (320)35.246.204.221 (320)159.100.30.125 (318)185.168.29.98 (313)77.81.65.244 (313)View all →

🏢 Same network: AS12574

View all →
12

Security Intelligence

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

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