
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 99 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 487 | Medium-risk: admin panels, config files | +60 | |
| Burst: 22 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 68 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 66 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 322 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 73 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 75 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger strong hits: 86 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 296 | Medium-risk: admin panels, config files | +60 | |
| Burst: 67 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 127 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 294 | Medium-risk: admin panels, config files | +60 | |
| Burst: 66 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 128 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 293 | Medium-risk: admin panels, config files | +60 | |
| Burst: 61 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 126 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 291 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 129 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 23 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 72 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 295 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 98 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 64 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 70 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 319 | Medium-risk: admin panels, config files | +60 | |
| Burst: 71 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 69 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 74 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 96 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 321 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 95 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 320 | Medium-risk: admin panels, config files | +60 |
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.151.224.126 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.151.224.126.
Block scanning from 20.151.224.126: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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.151.224.126 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:
IP address 20.151.224.126 has been traced to Toronto, Canada, operating on the network of Microsoft Corporation. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 6 days in our monitoring system, producing 29 flagged requests at a rate of ~4.8/day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 102 flagged addresses, Canada 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.
XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.