IP Threat Report
65.52.160.249
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger strong hits: 75 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 221 | Medium-risk: admin panels, config files | +60 | |
| Burst: 13 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 44 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 59 | Medium-risk: admin panels, config files | +60 | |
| Burst: 12 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 39 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 51 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 233 | Medium-risk: admin panels, config files | +60 | |
| Burst: 45 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 107 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 47 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 115 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 222 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 105 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 209 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 117 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 234 | Medium-risk: admin panels, config files | +60 | |
| Burst: 42 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 78 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 275 | Medium-risk: admin panels, config files | +60 | |
| Burst: 14 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Burst: 8 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 130 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 370 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 280 | Medium-risk: admin panels, config files | +60 | |
| Burst: 50 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 28 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 71 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 249 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 31 | Medium-risk: admin panels, config files | +60 | |
| Burst: 41 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 49 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 230 | Medium-risk: admin panels, config files | +60 | |
| Burst: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 53 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger strong hits: 219 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 441 | Medium-risk: admin panels, config files | +60 | |
| Burst: 52 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 301 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 664 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 26 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 119 | Medium-risk: admin panels, config files | +60 | |
| Burst: 40 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 161 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 158 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 442 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 38 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 10 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 47 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 235 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 150 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 281 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 86 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 66 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 175 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 105 | Medium-risk: admin panels, config files | +60 | |
| Burst: 49 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 68 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 353 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 106 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 122 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 104 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 421 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 227 | Medium-risk: admin panels, config files | +60 | |
| Burst: 54 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 55 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 222 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 443 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 29 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 199 | Medium-risk: admin panels, config files | +60 | |
| Burst: 48 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 22 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 28 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 65 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Burst: 16 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 56 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 51 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 87 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 224 | Medium-risk: admin panels, config files | +60 | |
| Burst: 46 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 60 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 267 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 40 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 160 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 440 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 64 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 164 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 48 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 109 | Medium-risk: admin panels, config files | +60 |
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 65.52.160.249 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 65.52.160.249: 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 65.52.160.249.
🔎 Path Enumeration Protection
Block scanning from 65.52.160.249: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
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 |
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
65.52.160.249 has been assigned a threat score of 280/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
IP address 65.52.160.249 has been traced to Hong Kong, Hong Kong, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 63 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~21 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 158 flagged addresses, Hong Kong represents a significant presence in our threat database. A score of 280/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
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.
💡 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.