IP Threat Report
20.203.138.185
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 102/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 104/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 112/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 114/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 121/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 127/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 128/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 132/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 134/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 136/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 137/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 139/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 142/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 144/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 145/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 151/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 153/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 154/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 155/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 156/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 157/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 162/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 172/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 184/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 187/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 190/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 194/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 195/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 32/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 35/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 42/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 43/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 52/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 53/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 54/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 55/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 57/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 60/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 160 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 264 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 266 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 320 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 333 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 334 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 399 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 462 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 530 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 111 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 140 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 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: 6 | 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 | |
| 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.203.138.185 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.203.138.185 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.203.138.185.
🤖 Bot Detection
Address UA spoofing from 20.203.138.185: 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.203.138.185 has been assigned a threat score of 280/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
Threat intelligence analysis has linked 20.203.138.185 to malicious activity originating from Zurich, Switzerland, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. During its 8-day observation window, we recorded 2,476 hostile requests from this IP — roughly 309.5 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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Our records show 112 malicious IPs originating from Switzerland, positioning it as a significant contributor to global threat activity. 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
🇨🇭 Top threats from Switzerland
34.65.117.95 (298)34.65.167.1 (288)20.203.149.15 (280)20.250.28.140 (280)20.250.9.235 (280)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.
💡 GDPR and Threat Intelligence
Processing IP addresses for security purposes under GDPR requires balancing legitimate interest in network protection with data minimization principles. Threat intelligence platforms must implement appropriate retention policies and provide mechanisms for data subject rights.