ABUSE.MOM
THREAT REPORT

IP Threat Report
64.233.172.168

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 07:18:20
First seen: 2026-10-10 02:25:04
Last seen: 2026-10-11 01:00:52
85

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
64.233.172.168
Type
Hosting
Country
🇺🇸 United States
City
Mountain View
ISP
Google LLC
Organization
Google LLC
Autonomous System
AS15169 Google LLC
Hit Count
20
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Probe 302→404Behavioral 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-10-10 02:25:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger strong hits: 2 (+50), Probe 302→404 (+20)
2026-10-11 01:00:52
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
AS15169 · 🇺🇸 United States

We have detected 171 malicious IPs from this autonomous system.

View all IPs from AS15169 →
06

Recommendations

Actions taken & recommended

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

07

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

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

10

Threat Analysis

64.233.172.168 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

Network traffic from 64.233.172.168, located in Mountain View, 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 20 hostile requests from this IP — roughly 20 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 36,315 blocked IPs in our database, making it a major source of malicious traffic. A threat score of 85/100 places this IP in the high-risk category. Blocking at the firewall level is 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: AS15169

35.217.44.155 (263)35.219.34.232 (263)35.219.245.67 (263)35.217.2.35 (263)35.213.167.158 (263)View all →
12

Security Intelligence

💡 Directory Traversal Attacks

Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

🔍 Check Any IP Address

Share this report: