IP Threat Report
172.213.10.221
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 88 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst: 42 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 88 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 184 | 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: 15 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 53 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 51 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 9 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 176 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 275 | Medium-risk: admin panels, config files | +60 | |
| Burst: 52 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 | |
| Burst: 47 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 167 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 16 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 55 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 276 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 15 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger medium hits: 314 | Medium-risk: admin panels, config files | +60 | |
| Burst: 53 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 166 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 59 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 200 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 54 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 189 req / 10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 10 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Burst: 52 req / 2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst: 160 req / 10s | Abnormally fast request rate — automated scanning | +35 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 172.213.10.221 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Other malicious IPs detected in the same /24 subnet — consider blocking 172.213.10.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 Bot Detection
Address UA spoofing from 172.213.10.221: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
🔎 Directory Scan Defense
IP 172.213.10.221 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 172.213.10.221 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 172.213.10.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Blacklist Status (DNSBL)
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.
Threat Analysis
172.213.10.221 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:
📊 Threat Analysis
Threat intelligence analysis has linked 172.213.10.221 to malicious activity originating from Milan, Italy, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. Over a period of 2 days, this IP generated 17 malicious requests, averaging approximately 8.5 requests per 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. Our records show 101 malicious IPs originating from Italy, positioning it as a significant contributor to global threat activity. 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.
Related Threats
Security Intelligence
💡 TLS Fingerprinting (JA3/JA4)
TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.
💡 Watering Hole Attack Strategy
Watering hole attacks compromise websites frequently visited by target organizations. Rather than attacking targets directly, adversaries infect trusted resources, exploiting the inherent trust users place in regularly visited sites.