ABUSE.MOM
THREAT REPORT

IP Threat Report
134.122.27.67

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 01:17:18
First seen: 2026-03-26 20:00:07
Last seen: 2026-05-24 10:19:41
95

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
134.122.27.67
Type
Hosting
Country
🇺🇸 United States
City
North Bergen
ISP
DigitalOcean, LLC
Organization
DigitalOcean, LLC
Autonomous System
AS14061 DigitalOcean, LLC
Hit Count
512
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Foreign refererReferer from unrelated external domain+10
Foreign referer seenReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 155
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-03-26 20:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Danger strong hits: 1 (+25)
2026-05-24 10:19:41
Last malicious request observed
Total score reached: 95/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 134.122.27.67 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

🔎 Directory Scan Defense

IP 134.122.27.67 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
cbl.abuseat.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
b.barracudacentral.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

134.122.27.67 has been assigned a threat score of 95/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

134.122.27.67 is registered in North Bergen, United States, operating on the network of DigitalOcean, LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 58 days, this IP generated 512 malicious requests, averaging approximately 8.8 requests per day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 128 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 95/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

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

💡 Insider Threat Indicators

Insider threats — whether malicious or negligent — account for a significant percentage of data breaches. Behavioral analytics detecting unusual access patterns, data downloads, and privilege escalation help identify insider risks before damage occurs.

🔍 Check Any IP Address

Share this report: