ABUSE.MOM
THREAT REPORT

IP Threat Report
34.186.255.35

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 10:56:31
First seen: 2026-05-08 05:00:04
Last seen: 2026-05-08 05:00:04
135

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
34.186.255.35
Type
Hosting
Country
🇺🇸 United States
City
Columbus
ISP
Google LLC
Organization
Google Cloud (us-east5)
Autonomous System
AS396982 Google LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Σ = 135
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-08 05:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 4 (+100), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-05-08 05:00:04
Last malicious request observed
Total score reached: 135/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 34.186.255.35 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 34.186.255.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 34.186.255.35 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

07

Neighbors in 34.186.255.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
ix.dnsbl.manitu.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com
✓ Clean
truncate.gbudb.net
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

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

Path Enumeration

📊 Threat Analysis

Network traffic from 34.186.255.35, located in Columbus, United States, operating on the network of Google LLC, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 143 flagged addresses, United States represents a significant presence in our threat database. At 135/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 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)34.136.84.236 (288)35.254.215.135 (288)35.243.110.60 (288)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Deception Technology Beyond Honeypots

Modern deception technology deploys fake credentials, decoy files, and breadcrumbs throughout production environments. When attackers interact with these deceptions, high-fidelity alerts trigger with virtually zero false positives.

🔍 Check Any IP Address

Share this report: