IP Threat Report
172.212.194.58
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| 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 111/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 13/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 15/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 16/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 17/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 18/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 21/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 22/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 25/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 37/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 40/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 | |
| Burst 52/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 53/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 55/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 57/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 59/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 6/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 60/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 61/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 64/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 67/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 68/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 69/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 70/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 71/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 72/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 73/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 74/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 75/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 76/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 77/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 78/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 79/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 122 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 125 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 136 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 142 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 144 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 160 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 194 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 196 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 202 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 216 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 222 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 240 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 25 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 272 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 288 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger medium hits: 304 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 314 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 333 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 360 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 362 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 363 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 364 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 366 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 41 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 432 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 50 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 52 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 62 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 63 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 72 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 75 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 78 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 97 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 34 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 36 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 46 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 5 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 51 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 57 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 60 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 62 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 64 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 65 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 66 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 67 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 68 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 69 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 76 | 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 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
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.212.194.58 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Path Enumeration Protection
Block scanning from 172.212.194.58: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 172.212.194.58 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🤖 Bot Detection
Address UA spoofing from 172.212.194.58: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
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.212.194.58 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
Our monitoring infrastructure has identified 172.212.194.58, geolocated to Des Moines, United States, operating on the network of Microsoft Corporation, as a source of suspicious network activity. Our sensors captured 9,407 malicious requests from this address across a 9-day span, reflecting a sustained attack cadence of ~1045.2 requests per 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. Our records show 108 malicious IPs originating from United States, 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
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.214.122 (350)34.187.158.4 (340)34.186.187.208 (340)104.28.214.116 (340)View all →Security Intelligence
💡 DDoS Mitigation Approaches
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.
💡 SQL Injection Campaigns
SQL injection remains one of the most common web attack vectors. Attackers inject malicious SQL code through input fields to extract database contents, modify data, or gain administrative access. Automated scanners test for SQLi vulnerabilities at massive scale.