IP Threat Report
180.211.113.210
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| POST requests present | Behavioral anomaly detected by automated analysis | +8 |
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 180.211.113.210 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 180.211.113.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Path Enumeration Protection
Block scanning from 180.211.113.210: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 180.211.113.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 88 | Unknown | Low | Service on port 88 |
| 4434 | Unknown | Low | Service on port 4434 |
| CVE ID | Link |
|---|---|
| CVE-2009-3767 | NVD → |
| CVE-2009-3765 | NVD → |
| CVE-2025-1220 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2025-14177 | NVD → |
| CVE-2023-6129 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2024-4577 | NVD → |
| CVE-2025-6491 | NVD → |
| CVE-2025-1736 | NVD → |
| CVE-2024-8932 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2013-2765 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2025-1219 | NVD → |
| CVE-2024-8927 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2025-66200 | NVD → |
| CVE-2025-1217 | NVD → |
| CVE-2009-1390 | NVD → |
| CVE-2025-14178 | NVD → |
| CVE-2023-38709 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2024-3566 | NVD → |
| CVE-2025-53020 | NVD → |
🔴 Security scanning identified 76 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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
180.211.113.210 has been assigned a threat score of 68/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.
The following attack categories were identified:
📊 Threat Analysis
IP address 180.211.113.210 has been traced to Ahmedabad, India, operating on the network of BlazeNet. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 106 malicious IPs originating from India, positioning it as a significant contributor to global threat activity. At 68/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.
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
Security Intelligence
💡 HTTP Request Smuggling
Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.
💡 SQL Injection Campaigns
SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.