ABUSE.MOM
THREAT REPORT

IP Threat Report
134.185.86.134

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 01:24:02
First seen: 2026-06-03 14:22:01
Last seen: 2026-07-30 01:12:43
265

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATHRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
134.185.86.134
Type
Unknown
Country
🇸🇬 Singapore
City
Singapore
ISP
Oracle Corporation
Organization
Oracle Corporation
Autonomous System
Unknown
Hit Count
8564
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
Burst 11/10sAbnormally fast request rate — automated scanning+35
Burst 11/2sAbnormally fast request rate — automated scanning+35
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 15/2sAbnormally fast request rate — automated scanning+35
Burst 16/2sAbnormally fast request rate — automated scanning+35
Burst 18/10sAbnormally fast request rate — automated scanning+35
Burst 29/10sAbnormally fast request rate — automated scanning+35
DDoS / FloodBehavioral anomaly detected by automated analysis+0
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Directory ScanBehavioral anomaly detected by automated analysis+0
Foreign refererReferer from unrelated external domain+10
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 615
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-06-03 14:22:01
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), Burst 11/10s (+35)
2026-07-30 01:12:43
Last malicious request observed
Total score reached: 265/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
06

Recommendations

Actions taken & recommended

  • IP 134.185.86.134 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 134.185.86.0/24
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Path Enumeration Protection

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

🌊 Traffic Flood Defense

IP 134.185.86.134 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 Bot Detection

Address UA spoofing from 134.185.86.134: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

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

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

10

Threat Analysis

134.185.86.134 has been assigned a threat score of 265/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 EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 134.185.86.134, geolocated to Singapore, Singapore, operating on the network of Oracle Corporation, as a source of suspicious network activity. Our sensors captured 8,564 malicious requests from this address across a 56-day span, reflecting a sustained attack cadence of ~152.9 requests per day. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 103 flagged addresses, Singapore represents a significant presence in our threat database. A score of 265/100 places this address in the top tier of severity. Block and investigate any historical connections.

11

Related Threats

🇸🇬 Top threats from Singapore

85.203.23.12 (340)103.167.150.231 (340)62.146.238.136 (340)85.203.23.31 (330)192.166.246.30 (325)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.

💡 Honeypot Network Intelligence

Honeypots are decoy systems designed to attract and study attackers. Networks of honeypots provide early warning of new attack campaigns, reveal attacker tools and techniques, and generate high-confidence threat intelligence with minimal false positives.

🔍 Check Any IP Address

Share this report: