
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 13/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 14/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 47/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 49/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1097 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 123 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 1490 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 158 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 168 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 1850 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2117 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 234 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 245 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 246 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2484 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 269 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2887 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 292 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2980 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2993 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 316 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 365 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 369 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 4374 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 438 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 471 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 505 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 538 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 630 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 118 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 126 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 157 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 212 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 23 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 26 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 27 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 312 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 331 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 35 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 421 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 425 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 460 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 61 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 617 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 88 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 9 | 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.
Block scanning from 20.206.67.15: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 20.206.67.15.
IP 20.206.67.15 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.206.67.15 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.206.67.15 has been traced to São Paulo, Brazil, 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 9 days in our monitoring system, producing 4,612 flagged requests at a rate of ~512.4/day. 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 diversity of 3 separate attack methods suggests a comprehensive attack toolkit — likely an automated scanner that tests for vulnerabilities across multiple categories. Brazil currently accounts for 13 blocked IPs in our database, making it a notable 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.
Machine learning models analyze vast amounts of network traffic to identify attack patterns invisible to rule-based systems. Supervised models classify known attack types while unsupervised models detect anomalies that may indicate novel threats.