ABUSE.MOM
THREAT REPORT

IP Threat Report
34.162.248.60

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-21 23:57:50
First seen: 2026-05-05 06:00:04
Last seen: 2026-05-05 06:00:04
85

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

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

07

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

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

10

Threat Analysis

34.162.248.60 has been assigned a threat score of 85/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 Enumeration

📊 Threat Analysis

IP address 34.162.248.60 has been traced to Columbus, United States, operating on the network of Google LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. 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 IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 143 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. The score of 85/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

💡 Submarine Cable and Internet Exchange Points

Internet traffic routing through a limited number of submarine cables and exchange points creates natural chokepoints. Understanding these routing patterns helps explain geographic clustering of certain attack types and latency-based scanning behaviors.

🔍 Check Any IP Address

Share this report: