
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 107/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 14/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 17/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 19/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 20/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 25/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 27/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 28/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 30/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 32/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 35/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 36/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 38/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 38/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 39/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 41/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 42/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 42/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 43/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 44/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 45/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 46/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/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 91/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 124 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 130 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 134 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 136 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 138 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 139 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 181 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 32 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 36 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 38 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 41 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 42 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 43 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 45 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 47 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 49 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 78 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 80 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 82 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 89 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 90 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 92 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 96 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 98 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 10 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 13 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 16 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 17 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 20 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 21 | 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: 29 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 5 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 |
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 172.213.2.180: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
IP 172.213.2.180 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
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.
172.213.2.180 has been assigned a threat score of 255/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:
Our monitoring infrastructure has identified 172.213.2.180, geolocated to Milan, Italy, operating on the network of Microsoft Corporation, as a source of suspicious network activity. The address has been active for 8 days in our monitoring system, producing 5,158 flagged requests at a rate of ~644.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 dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 112 flagged addresses, Italy represents a significant presence in our threat database. At 255/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.
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.
MFA dramatically reduces the effectiveness of credential-based attacks. Even when passwords are compromised through phishing or data breaches, the additional authentication factor prevents unauthorized access in the vast majority of cases.