
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 43 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 341 | Medium-risk: admin panels, config files | +60 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Burst: 30 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 97 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 346 | Medium-risk: admin panels, config files | +60 | |
| Burst: 43 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 131 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Burst: 32 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 96 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 58 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 519 | Medium-risk: admin panels, config files | +60 | |
| Burst: 31 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 98 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 34 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 105 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 108 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 37 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 125 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 36 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 127 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.
Address UA spoofing from 172.213.136.102: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Block scanning from 172.213.136.102: 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 172.213.136.102.
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.136.102 has been assigned a threat score of 280/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
Network traffic from 172.213.136.102, located in Milan, Italy, operating on the network of Microsoft Corporation, has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 8 flagged requests at a rate of ~8/day. 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. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 101 flagged addresses, Italy represents a significant presence in our threat database. 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.
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.
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.