IP Threat Report
20.65.105.233
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 16/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 17/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 17/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 22/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 23/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 24/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 25/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 56/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 74/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 77/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 78/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 79/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 80/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 81/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 82/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 83/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 84/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 85/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 86/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 87/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 88/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 89/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 90/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 91/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1012 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 133 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 147 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 160 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 17 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 266 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 293 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger medium hits: 304 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 306 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 308 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 320 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 334 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 344 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 378 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 399 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 402 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 480 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 501 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 516 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 600 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 610 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 626 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 640 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 654 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 668 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 678 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 882 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 900 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 906 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 920 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 102 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 106 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 110 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 131 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 140 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 146 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 167 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 187 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 188 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 192 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 199 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 47 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 49 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 73 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 94 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 98 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +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 20.65.105.233 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 20.65.105.233 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.65.105.233.
🤖 Bot Detection
Address UA spoofing from 20.65.105.233: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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
20.65.105.233 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
Our monitoring infrastructure has identified 20.65.105.233, geolocated to Boydton, United States, operating on the network of Microsoft Corporation, as a source of suspicious network activity. During its 8-day observation window, we recorded 8,585 hostile requests from this IP — roughly 1073.1 per day on average. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 108 flagged addresses, United States represents a significant presence in our threat database. At 280/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →Security Intelligence
💡 DDoS Mitigation Approaches
Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.
💡 Server-Side Request Forgery (SSRF)
SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.