IP Threat Report
217.216.65.202
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA bot: python | Known bot/crawler User-Agent detected | +40 | |
| Danger strong hits: 71 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Burst: 10 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 29 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 26 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 79 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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 217.216.65.202 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
🤖 Bot Detection
Address UA spoofing from 217.216.65.202: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 217.216.65.202.
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 |
| CVE ID | Link |
|---|---|
| CVE-2025-66200 | NVD → |
| CVE-2024-40898 | NVD → |
| CVE-2024-42516 | NVD → |
| CVE-2025-23048 | NVD → |
| CVE-2009-2299 | NVD → |
| CVE-2012-3526 | NVD → |
| CVE-2013-0941 | NVD → |
| CVE-2024-38473 | NVD → |
| CVE-2013-0942 | NVD → |
| CVE-2024-39573 | NVD → |
| CVE-2025-58098 | NVD → |
| CVE-2024-24795 | NVD → |
| CVE-2013-4365 | NVD → |
| CVE-2011-2688 | NVD → |
| CVE-2024-38472 | NVD → |
| CVE-2024-38477 | NVD → |
| CVE-2009-0796 | NVD → |
| CVE-2024-38475 | NVD → |
| CVE-2011-1176 | NVD → |
| CVE-2025-59775 | NVD → |
| CVE-2025-49812 | NVD → |
| CVE-2024-38474 | NVD → |
| CVE-2024-47252 | NVD → |
| CVE-2025-65082 | NVD → |
| CVE-2013-2765 | NVD → |
🔴 This host has 37 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
217.216.65.202 has been assigned a threat score of 270/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
📊 Threat Analysis
The address 217.216.65.202 originates from Orangeburg, United States, operating on the network of Contabo Inc.. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 1 days in our monitoring system, producing 2 flagged requests at a rate of ~2/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (User-Agent Anomaly and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. United States currently accounts for 118 blocked IPs in our database, making it a significant source of malicious traffic. A score of 270/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →Security Intelligence
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 Business Email Compromise Tactics
BEC attacks use compromised or spoofed executive email accounts to request fraudulent wire transfers or sensitive data. These attacks cause billions in annual losses and rely on social engineering rather than technical exploitation.