
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst 143/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 170/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 171/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 172/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 173/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 178/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 179/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 182/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 184/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 185/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 187/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 189/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 190/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 192/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 193/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 196/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 198/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 199/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | 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 57/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 61/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 71/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 72/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 73/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 | |
| Danger medium hits: 149 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 185 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 186 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 278 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 370 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 109 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 120 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 60 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 68 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 79 | 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.142.140 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 20.113.142.140 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Address UA spoofing from 20.113.142.140: 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.142.140 has been assigned a threat score of 280/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
The address 20.113.142.140 originates from Frankfurt am Main, Germany, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 9-day observation window, we recorded 2,406 hostile requests from this IP — roughly 267.3 per day on average. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 151 malicious IPs originating from Germany, positioning it as a significant contributor to global threat activity. A score of 280/100 places this address in the top tier of severity. Block and investigate any historical connections.
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 vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.