ABUSE.MOM
THREAT REPORT

IP Threat Report
34.182.226.134

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 18:59:29
First seen: 2026-04-20 18:00:05
Last seen: 2026-04-20 18:00:05
155

⛔ Verdict: BLOCK

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

DANGER_PATHBURST
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 18Medium-risk: admin panels, config files+60
Burst: 18 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 20 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 155
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-04-20 18:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 18 (+60), Burst: 18 req / 2s (+35)
2026-04-20 18:00:05
Last malicious request observed
Total score reached: 155/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.182.226.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 34.182.226.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🌊 Traffic Flood Defense

IP 34.182.226.134 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

07

Neighbors in 34.182.226.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
bl.spamcop.net
✓ Clean
zen.spamhaus.org
✓ 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.182.226.134 has been assigned a threat score of 155/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:

Request Flooding

📊 Threat Analysis

34.182.226.134 is registered in Washington, United States, operating on the network of Google LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 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 IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 143 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 155/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)34.22.208.175 (285)34.166.187.0 (285)34.128.70.180 (285)View all →
12

Security Intelligence

💡 Credential Stuffing at Scale

Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.

💡 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.

🔍 Check Any IP Address

Share this report: