ABUSE.MOM
THREAT REPORT

IP Threat Report
138.68.62.66

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 16:50:36
First seen: 2026-02-18 07:00:06
Last seen: 2026-05-06 22:00:07
105

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
138.68.62.66
Type
Hosting
Country
🇺🇸 United States
City
Santa Clara
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 5Medium-risk: admin panels, config files+50
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Σ = 130
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-02-18 07:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 5 (+50), 404 ratio >= 60% (+25), Probe pattern 302->404 same path (+20)
2026-05-06 22:00:07
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

DigitalOcean, LLC
AS14061 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 138.68.62.66 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 138.68.62.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 138.68.62.66: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

07

Neighbors in 138.68.62.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
Spamhaus ZEN

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

10

Threat Analysis

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

📊 Threat Analysis

IP address 138.68.62.66 has been traced to Santa Clara, United States, operating on the network of DigitalOcean, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 2 malicious requests from this address across a 77-day span, reflecting a sustained attack cadence of ~0 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 129 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

129.212.237.216 (308)168.144.34.140 (295)170.64.203.182 (280)161.35.89.38 (273)64.226.94.117 (273)View all →
12

Security Intelligence

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

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