
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst 136/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 160/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 165/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 186/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 191/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 59/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 60/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 63/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 64/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 65/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 67/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 68/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 69/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 70/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 71/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 72/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 74/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 75/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 76/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 77/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 134 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 288 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 312 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 432 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 468 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 882 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 22 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 29 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 40 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 43 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 86 | 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.52.171.102: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 20.52.171.102 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 20.52.171.102: 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.52.171.102 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:
Network traffic from 20.52.171.102, located in Frankfurt am Main, Germany, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. The address has been active for 12 days in our monitoring system, producing 5,066 flagged requests at a rate of ~422.2/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 151 flagged addresses, Germany represents a significant 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.
WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.