ABUSE.MOM
THREAT REPORT

IP Threat Report
34.176.205.104

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-29 03:07:38
First seen: 2026-05-15 07:00:06
Last seen: 2026-05-15 07:00:06
120

⛔ Verdict: BLOCK

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

UA_CHANGEDDANGER_PATHBURST
01

Geolocation & Classification

IP Address
34.176.205.104
Type
Hosting
Country
🇨🇱 CL
City
Santiago
ISP
Google LLC
Organization
Google Cloud (southamerica-west1)
Autonomous System
AS396982 Google LLC
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Burst: 10 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 10 req / 10sAbnormally fast request rate — automated scanning+35
Σ = 120
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-05-15 07:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Danger strong hits: 1 (+25), Burst: 10 req / 2s (+35)
2026-05-15 07:00:06
Last malicious request observed
Total score reached: 120/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Google LLC
AS396982 · 🇨🇱 CL
06

Recommendations

Actions taken & recommended

  • IP 34.176.205.104 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

🤖 User-Agent Anomaly Defense

IP 34.176.205.104 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 34.176.205.104.

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
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

34.176.205.104 has been assigned a threat score of 120/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 34.176.205.104, geolocated to Santiago, CL, operating on the network of Google LLC, as a source of suspicious network activity. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~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 dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 52 flagged addresses, CL represents a notable presence in our threat database. A score of 120/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 CL

34.176.84.235 (263)149.88.104.35 (255)34.176.250.253 (195)34.176.236.109 (195)34.176.217.5 (195)View all →

🏢 Same network: AS396982

34.176.84.235 (263)34.176.250.253 (195)34.176.236.109 (195)34.176.217.5 (195)34.176.13.96 (145)View all →
12

Security Intelligence

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

💡 Mobile Network Threat Landscape

Mobile carrier NAT (CGNAT) means thousands of users share a single public IP, making mobile IPs unreliable for reputation scoring. However, mobile networks are increasingly used as attack platforms through compromised apps and malicious SDKs.

🔍 Check Any IP Address

Share this report: