IP Threat Report
20.193.50.139
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 10/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 11/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 20/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 22/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 28/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 29/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 30/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 31/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 32/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 33/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 34/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 35/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 36/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 77/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 9/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 101 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 11 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 110 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 120 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 155 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 156 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 158 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 159 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 20 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 200 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 202 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 209 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 211 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 213 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 218 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 22 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 224 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 233 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 237 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 250 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 253 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 260 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 266 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 272 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 28 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 30 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 305 | 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: 32 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 33 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 336 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 375 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 376 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 426 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 43 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 4364 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 50 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 52 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 538 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 60 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 670 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 80 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 88 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 90 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 10 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 11 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 13 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 15 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 22 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2520 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 46 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | 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
We have detected 1854 malicious IPs from this autonomous system.
Recommendations
Actions taken & recommended
- IP 20.193.50.139 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
🔎 Path Enumeration Protection
Block scanning from 20.193.50.139: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.193.50.139.
🤖 Bot Detection
Address UA spoofing from 20.193.50.139: 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.193.50.139 has been assigned a threat score of 280/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
20.193.50.139 is registered in The Rocks, Australia, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 5,012 malicious requests from this address across a 10-day span, reflecting a sustained attack cadence of ~501.2 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 diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Australia currently accounts for 1,240 blocked IPs in our database, making it a major source of malicious traffic. 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 Australia
137.23.3.14 (310)20.92.77.159 (310)3.26.255.172 (308)3.26.98.5 (308)35.189.4.156 (298)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.
💡 DNS Sinkholing for Malware Defense
DNS sinkholing redirects queries for known malicious domains to controlled IP addresses. This technique blocks malware communication, prevents data exfiltration, and identifies compromised internal hosts attempting to contact command-and-control servers.