ABUSE.MOM
THREAT REPORT

IP Threat Report
35.195.8.90

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-14 14:03:35
First seen: 2026-08-16 22:40:35
Last seen: 2026-08-23 02:07:14
298

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 298/100. Total malicious requests observed: 523.

BURSTDANGER_PATHMETHODRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
35.195.8.90
Type
Hosting
Country
🇧🇪 Belgium
City
Brussels
ISP
Google LLC
Organization
Google Cloud (europe-west1)
Autonomous System
AS396982 Google LLC
Hit Count
523
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 149/2sAbnormally fast request rate — automated scanning+35
Burst 176/10sAbnormally fast request rate — automated scanning+35
Burst 176/2sAbnormally fast request rate — automated scanning+35
Burst 200/10sAbnormally fast request rate — automated scanning+35
Burst 200/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 14Medium-risk: admin panels, config files+60
Danger medium hits: 21Medium-risk: admin panels, config files+60
Danger medium hits: 7Medium-risk: admin panels, config files+60
Danger strong hits: 31High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 62High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 75High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 77High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 93High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 923
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-08-16 22:40:35
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 149/2s (+35), Burst 176/10s (+35)
2026-08-23 02:07:14
Last malicious request observed
Total score reached: 298/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇧🇪 Belgium
06

Recommendations

Actions taken & recommended

  • IP 35.195.8.90 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 35.195.8.90 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

IP 35.195.8.90 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 35.195.8.90: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
bl.blocklist.de
✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

35.195.8.90 has been assigned a threat score of 298/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:

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 35.195.8.90 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. During its 6-day observation window, we recorded 523 hostile requests from this IP — roughly 87.2 per day on average. 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 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 101 malicious IPs originating from Belgium, positioning it as a significant contributor to global threat activity. At 298/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.

11

Related Threats

🇧🇪 Top threats from Belgium

34.78.110.28 (348)34.52.216.81 (313)34.38.157.42 (313)34.78.158.246 (313)34.156.192.235 (313)View all →

🏢 Same network: AS396982

34.78.110.28 (348)136.67.84.210 (340)34.74.191.44 (340)136.67.103.22 (340)34.52.216.81 (313)View all →
12

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.

💡 Container Security Challenges

Containerized applications face unique security challenges including vulnerable base images, excessive privileges, shared kernel attacks, and insecure orchestration configurations. Runtime security monitoring and immutable container policies mitigate these risks.

🔍 Check Any IP Address

Share this report: