
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 105/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 109/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 131/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 135/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 142/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 147/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 151/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 157/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 162/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 163/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 164/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 167/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 168/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 174/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 175/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 182/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 186/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 187/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 42/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/2s | 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 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 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 71/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 76/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 96/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 143 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 163 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 185 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 245 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 428 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 448 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 675 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 93 | Medium-risk: admin panels, config files | +60 | |
| 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: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 56 | 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.113.56.22 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.113.56.22.
Address UA spoofing from 20.113.56.22: 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.113.56.22 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.113.56.22 is registered in Frankfurt am Main, Germany, operating on the network of Microsoft Corporation. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 3 days, this IP generated 3,032 malicious requests, averaging approximately 1010.7 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 diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Our records show 107 malicious IPs originating from Germany, positioning it as a significant contributor to global threat activity. 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.
The impact of data breaches extends beyond immediate financial losses. Regulatory fines, legal liability, reputational damage, and customer churn create long-term costs that often exceed the direct costs of incident response and remediation.