IP Threat Report
35.189.229.134
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 | |
| Burst 112/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 112/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 115/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 115/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 124/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 128/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 128/2s | 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 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Danger strong hits: 151 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 71 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 72 | 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: 77 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 79 | 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 35.189.229.134 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 35.189.229.0/24
- 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 35.189.229.134 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Flood / DDoS Mitigation
Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 35.189.229.134.
🤖 User-Agent Anomaly Defense
IP 35.189.229.134 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
Neighbors in 35.189.229.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
35.189.229.134 has been assigned a threat score of 273/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
IP address 35.189.229.134 has been traced to Brussels, Belgium, operating on the network of Google LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 23 days, this IP generated 1,137 malicious requests, averaging approximately 49.4 requests per 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 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 842 malicious IPs originating from Belgium, positioning it as a major contributor to global threat activity. At 273/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.
💡 Responsible Disclosure Ethics
Responsible disclosure balances public safety with giving vendors time to patch vulnerabilities. The security community generally supports coordinated disclosure timelines, but disagreements about appropriate timeframes and full disclosure continue to drive policy debates.