IP Threat Report
58.216.109.17
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 8 | Medium-risk: admin panels, config files | +60 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
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 58.216.109.17 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 58.216.109.0/24
- 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 58.216.109.17 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
Neighbors in 58.216.109.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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 161 | Unknown | Low | Service on port 161 |
| 800 | Unknown | Low | Service on port 800 |
| 843 | Unknown | Low | Service on port 843 |
| 902 | Unknown | Low | Service on port 902 |
| 5600 | Unknown | Low | Service on port 5600 |
| 8001 | Unknown | Low | Service on port 8001 |
| 8043 | Unknown | Low | Service on port 8043 |
| 8068 | Unknown | Low | Service on port 8068 |
| 8069 | Unknown | Low | Service on port 8069 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8081 | Unknown | Low | Service on port 8081 |
| 8089 | Unknown | Low | Service on port 8089 |
| 8099 | Unknown | Low | Service on port 8099 |
| 8443 | HTTPS-Alt | Low | Service on port 8443 |
| 9101 | Unknown | Low | Service on port 9101 |
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
58.216.109.17 has been assigned a threat score of 70/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
📊 Threat Analysis
Network traffic from 58.216.109.17, located in Nanjing, China, operating on the network of China Telecom, has been classified as malicious by our automated threat scoring engine. During its 34-day observation window, we recorded 2 hostile requests from this IP — roughly 0.1 per day on average. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. China currently accounts for 105 blocked IPs in our database, making it a significant source of malicious traffic. The score of 70/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
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 China
180.184.55.222 (340)117.50.120.215 (235)115.191.1.205 (235)123.58.16.244 (235)43.142.47.248 (230)View all →🏢 Same network: AS140293
218.93.165.108 (80)58.216.109.13 (70)58.216.109.8 (70)58.216.109.18 (70)View all →Security Intelligence
💡 Credential Stuffing at Scale
Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.
💡 GraphQL Security Risks
GraphQL APIs introduce specific vulnerabilities including introspection information disclosure, query complexity attacks, batching abuse, and authorization bypass through nested queries. Depth limiting, cost analysis, and field-level authorization address these GraphQL-specific threats.