
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 109/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 113/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 139/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 17/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 18/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 19/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 20/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 21/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 27/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 33/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 51/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 53/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 54/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 56/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 57/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 59/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 61/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 64/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 65/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 67/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 68/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 69/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 70/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 71/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 72/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 73/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 74/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 76/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 1304 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 1324 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 1325 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 1338 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 1782 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 1910 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 201 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 223 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2424 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2425 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 322 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 423 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 424 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 425 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 428 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 435 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 436 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 437 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 438 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 440 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 442 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 443 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 444 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 445 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 446 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 447 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 448 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 55 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 645 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 666 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 671 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 673 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 860 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 880 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 881 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 887 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 892 | 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: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 13 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 19 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 27 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 35 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 5 | 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 | |
| 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.
Block scanning from 20.9.82.255: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.9.82.255.
IP 20.9.82.255 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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.9.82.255 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:
20.9.82.255 is registered in Des Moines, United States, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 6,196 malicious requests from this address across a 3-day span, reflecting a sustained attack cadence of ~2065.3 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 17 flagged addresses, United States represents a notable presence in our threat database. 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.