ABUSE.MOM
THREAT REPORT

IP Threat Report
34.0.156.113

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 23:28:23
First seen: 2026-04-07 17:00:08
Last seen: 2026-04-07 17:00:08
90

⛔ Verdict: BLOCK

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

REDIRECT_PROBEBURST
01

Geolocation & Classification

IP Address
34.0.156.113
Type
Hosting
Country
🇺🇸 United States
City
Dallas
ISP
Google LLC
Organization
Google Cloud (us-south1)
Autonomous System
AS15169 Google LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 10 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 90
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-07 17:00:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Probe pattern 302->404 same path (+20), Burst: 6 req / 2s (+35), Burst: 10 req / 10s (+35)
2026-04-07 17:00:08
Last malicious request observed
Total score reached: 90/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS15169 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

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

09

Blacklist Status (DNSBL)

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

✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
psbl.surriel.com
✓ Clean
b.barracudacentral.org
✓ 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.0.156.113 has been assigned a threat score of 90/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 Flooding

📊 Threat Analysis

Network traffic from 34.0.156.113, located in Dallas, United States, operating on the network of Google LLC, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. United States currently accounts for 201 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 90/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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: AS15169

66.249.82.32 (205)74.125.217.40 (175)192.178.11.96 (170)35.212.230.168 (170)209.85.238.2 (165)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.

💡 Botnet Command and Control Evolution

Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.

🔍 Check Any IP Address

Share this report: