ABUSE.MOM
THREAT REPORT

IP Threat Report
136.109.86.167

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:04:03
First seen: 2026-05-09 21:00:06
Last seen: 2026-05-30 06:57:29
115

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
136.109.86.167
Type
Hosting
Country
🇺🇸 United States
City
The Dalles
ISP
Google LLC
Organization
Google Cloud (us-west1)
Autonomous System
AS396982 Google LLC
Hit Count
577
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 6High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 7High-risk paths: shells, RCE vectors, exploits+100
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 385
03

Observed Activity

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

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

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

04

Timeline

2026-05-09 21:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger strong hits: 2 (+50), Danger strong hits: 4 (+100)
2026-05-30 06:57:29
Last malicious request observed
Total score reached: 115/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

07

Neighbors in 136.109.86.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

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
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

136.109.86.167 has been assigned a threat score of 115/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 Enumeration

📊 Threat Analysis

136.109.86.167 is registered in The Dalles, United States, operating on the network of Google LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 20-day observation window, we recorded 577 hostile requests from this IP — roughly 28.9 per day on average. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 141 flagged addresses, United States represents a significant presence in our threat database. A score of 115/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS396982

34.187.158.4 (340)34.186.187.208 (340)35.243.110.60 (288)34.136.84.236 (288)35.254.215.135 (288)View all →
12

Security Intelligence

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 Residential Proxy Networks

Residential proxies route traffic through real home internet connections, making malicious traffic appear to come from legitimate users. Some networks install proxy software bundled with free applications, unknowingly conscripting millions of devices.

🔍 Check Any IP Address

Share this report: