IP Threat Report
213.202.225.11
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Danger medium hits: 8 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 213.202.225.11 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 213.202.225.11 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 6379 | Redis | Critical | Redis in-memory database — frequently misconfigured without auth |
| 8066 | Unknown | Low | Service on port 8066 |
| 8090 | Unknown | Low | Service on port 8090 |
| 8891 | Unknown | Low | Service on port 8891 |
⚠️ Network scanning reveals 1 dangerous service exposed on 213.202.225.11. Open database ports suggest possible data exfiltration risk. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2013-4365 | NVD → |
| CVE-2025-6491 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2025-14180 | NVD → |
| CVE-2025-55753 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2025-1735 | NVD → |
| CVE-2007-4723 | NVD → |
| CVE-2013-2220 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2012-3526 | NVD → |
| CVE-2025-14178 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2025-49630 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2025-14177 | NVD → |
| CVE-2007-3205 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2025-53020 | NVD → |
| CVE-2025-1220 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2012-4001 | NVD → |
| CVE-2009-0796 | NVD → |
🔴 This host has 34 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
213.202.225.11 has been assigned a threat score of 105/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:
📊 Threat Analysis
The address 213.202.225.11 originates from Düsseldorf, Germany, operating on the network of WIIT AG. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 8 days, this IP generated 3 malicious requests, averaging approximately 0.4 requests per day. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Germany currently accounts for 105 blocked IPs in our database, making it a significant source of malicious traffic. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
Related Threats
🇩🇪 Top threats from Germany
15.220.152.241 (320)77.81.65.244 (313)185.168.29.98 (313)91.217.249.222 (305)212.30.36.219 (305)View all →🏢 Same network: AS24961
213.202.253.4 (285)89.163.146.197 (195)89.163.151.66 (95)83.136.82.87 (70)View all →Security Intelligence
💡 WordPress-Specific Attack Vectors
WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.
💡 VPN Exit Node Reputation
VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.