ABUSE.MOM
THREAT REPORT

IP Threat Report
34.75.115.119

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-10 19:44:53
First seen: 2026-09-05 20:10:21
Last seen: 2026-10-10 19:39:03
290

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEUA_CHANGEDUA_SUS
01

Geolocation & Classification

IP Address
34.75.115.119
Type
Hosting
Country
🇺🇸 United States
City
North Charleston
ISP
Google LLC
Organization
Google Cloud (us-east1)
Autonomous System
AS396982 Google LLC
Hit Count
2492
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 23/2sAbnormally fast request rate — automated scanning+35
Burst 84/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 6Medium-risk: admin panels, config files+60
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 10High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 11High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 12High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 13High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 14High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 15High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 16High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 17High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 18High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 19High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 20High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 21High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 22High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 23High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 5High-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
Danger strong hits: 71High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 8High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA changedMultiple User-Agents — bot rotation technique+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 2280
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-09-05 20:10:21
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 23/2s (+35), Burst 84/10s (+35)
2026-10-10 19:39:03
Last malicious request observed
Total score reached: 290/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.75.115.119 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.75.115.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

Block scanning from 34.75.115.119: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

🌊 Flood / DDoS Mitigation

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

🤖 User-Agent Anomaly Defense

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

07

Neighbors in 34.75.115.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
psbl.surriel.com
✓ Clean
zen.spamhaus.org
✓ Clean
cbl.abuseat.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org
✓ Clean
b.barracudacentral.org

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

10

Threat Analysis

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

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 34.75.115.119, geolocated to North Charleston, United States, operating on the network of Google LLC, as a source of suspicious network activity. The address has been active for 34 days in our monitoring system, producing 2,492 flagged requests at a rate of ~73.3/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 combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 130 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 290/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.214.122 (350)216.73.160.52 (350)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS396982

34.78.110.28 (348)136.67.84.210 (340)34.74.191.44 (340)136.67.103.22 (340)35.254.195.37 (340)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.

💡 Ransomware-as-a-Service Economy

The RaaS model allows technically unskilled criminals to deploy sophisticated ransomware through affiliate programs. Operators provide the malware, infrastructure, and negotiation services, taking a percentage of ransom payments from their affiliates.

🔍 Check Any IP Address

Share this report: