
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 100/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 104/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 110/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 111/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 114/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 115/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/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 130/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 131/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 136/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 139/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 144/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 146/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 148/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 150/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 162/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 165/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 168/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 170/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 184/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 188/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 37/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 42/10s | 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/10s | 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 51/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 56/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 57/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 61/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/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 71/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 74/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 8/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 84/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 93/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 94/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 96/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 99/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 100 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 104 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 111 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 112 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 114 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 122 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 125 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 126 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 141 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 159 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 174 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 178 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 183 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 196 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 200 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 204 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 266 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 349 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 37 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 42 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 47 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 74 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 84 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 94 | 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: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| 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: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 7 | 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.
IP 20.52.217.208 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 20.52.217.208 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
IP 20.52.217.208 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.52.217.208 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 intelligence analysis has linked 20.52.217.208 to malicious activity originating from Frankfurt am Main, Germany, 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 5,341 hostile requests from this IP — roughly 667.6 per day on average. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. Germany currently accounts for 103 blocked IPs in our database, making it a significant 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.
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.