
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 183 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 54 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 158 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 366 | Medium-risk: admin panels, config files | +60 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 60 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 200 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 372 | Medium-risk: admin panels, config files | +60 | |
| Burst: 56 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 374 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 59 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 187 | Medium-risk: admin panels, config files | +60 | |
| Burst: 58 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 161 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 364 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 70 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 546 | Medium-risk: admin panels, config files | +60 | |
| Burst: 191 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 61 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 62 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 195 req / 10s | Abnormally fast request rate — automated scanning | +35 |
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.111.57.125 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
IP 20.111.57.125 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.111.57.125.
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.111.57.125 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:
IP address 20.111.57.125 has been traced to Paris, France, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 1-day observation window, we recorded 14 hostile requests from this IP — roughly 14 per day on average. 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 201 flagged addresses, France represents a significant presence in our threat database. At 280/100, this is an extremely high-risk address. All traffic should be considered hostile.
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.
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.