IP Threat Report
4.204.224.164
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 16/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 22/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 23/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 24/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 25/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 50/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 79/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 80/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 81/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 82/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 83/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 84/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 85/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 86/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 87/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 88/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 89/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 108 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 121 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 122 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 123 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 125 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 128 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 135 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 137 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 152 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 154 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 156 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 172 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 182 | 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: 203 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 204 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 210 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 215 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 224 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 225 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 231 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 236 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 239 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 248 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 256 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 258 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 262 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 274 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 278 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 279 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger medium hits: 300 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 304 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 306 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 326 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 342 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 352 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 358 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 360 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 370 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 373 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 411 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 415 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 424 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 430 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 44 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 450 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 460 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 466 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 489 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 49 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 504 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 510 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 530 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 539 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 542 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 56 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 632 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 687 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 701 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 708 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 725 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 758 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 78 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 82 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 84 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 931 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 966 | 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: 120 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 121 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 14 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 15 | 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: 18 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 19 | 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: 22 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 23 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 25 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 27 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 28 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 30 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 32 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| 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: 38 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 39 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 4 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 40 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 45 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 48 | 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: 54 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 55 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 56 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 58 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 59 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 64 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 68 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 7 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 70 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 75 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 8 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 84 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 90 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 93 | 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 4.204.224.164 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
🔎 Directory Scan Defense
IP 4.204.224.164 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 4.204.224.164 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 4.204.224.164: 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
4.204.224.164 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:
📊 Threat Analysis
The address 4.204.224.164 originates from Toronto, Canada, operating on the network of Microsoft Corporation. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 13 days, this IP generated 13,407 malicious requests, averaging approximately 1031.3 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. With 101 flagged addresses, Canada represents a significant presence in our threat database. At 280/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.
Related Threats
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.
💡 TLS Certificate Misconfigurations
Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.