
ABUSE.MOM — BEHAVE OR GET EXPOSED
| 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 26/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 28/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 8/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 9/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 105 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 108 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 109 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 120 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 122 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 123 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 124 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 128 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 130 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 132 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 133 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 134 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 138 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 158 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 160 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 176 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 180 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 186 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 192 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 195 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 201 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 204 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 207 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 213 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 220 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 228 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 240 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 246 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 248 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 250 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 258 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 262 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 27 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 304 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 314 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 360 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 364 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 369 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 370 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 380 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 390 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 435 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 438 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 480 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 486 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 606 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 61 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 64 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 66 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 68 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 70 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 708 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 72 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 738 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 88 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 10 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 100 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 128 | 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: 161 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 17 | 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: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 38 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 40 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 41 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 45 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 5 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 53 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 54 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 58 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 62 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 66 | 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 | |
| Danger strong hits: 80 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 9 | 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 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
We have detected 1852 malicious IPs from this autonomous system.
Block scanning from 20.211.90.37: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 20.211.90.37 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 20.211.90.37: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.
20.211.90.37 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:
Our monitoring infrastructure has identified 20.211.90.37, geolocated to The Rocks, Australia, operating on the network of Microsoft Corporation, as a source of suspicious network activity. The address has been active for 14 days in our monitoring system, producing 7,832 flagged requests at a rate of ~559.4/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. With a threat score of 280/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
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.
Internet traffic routing through a limited number of submarine cables and exchange points creates natural chokepoints. Understanding these routing patterns helps explain geographic clustering of certain attack types and latency-based scanning behaviors.