IP Threat Report
207.175.220.59
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 112/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 112/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 116/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 116/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 117/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 117/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 120/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 120/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 122/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 122/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 123/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 124/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 124/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 127/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 129/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 130/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 131/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 131/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 132/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 132/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 200/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 97/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 20 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 22 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Danger strong hits: 123 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 127 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 128 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 144 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 72 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 73 | 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: 76 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 80 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
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 207.175.220.59 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 207.175.220.59 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 207.175.220.59 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 207.175.220.59: 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
207.175.220.59 has been assigned a threat score of 280/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 207.175.220.59, located in Brussels, Belgium, operating on the network of Google LLC, has been classified as malicious by our automated threat scoring engine. Over a period of 41 days, this IP generated 3,095 malicious requests, averaging approximately 75.5 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 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 844 malicious IPs originating from Belgium, positioning it as a major 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
💡 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.
💡 Tor Exit Node Detection
Tor exit nodes are publicly listed but constantly rotating. While Tor serves essential privacy functions for journalists and activists, it is also used to anonymize attacks. Effective security policies differentiate between blocking and monitoring Tor traffic.