ABUSE.MOM
THREAT REPORT

IP Threat Report
134.199.224.179

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:21:56
First seen: 2026-02-25 02:00:06
Last seen: 2026-02-25 02:00:06
230

⛔ Verdict: BLOCK

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

BOT_UADANGER_PATHRATIO_404REDIRECT_PROBEBURST
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
UA bot: scannerKnown bot/crawler User-Agent detected+40
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
Danger medium hits: 2Medium-risk: admin panels, config files+20
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 230
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-02-25 02:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA bot: scanner (+40), Danger strong hits: 5 (+100), Danger medium hits: 2 (+20)
2026-02-25 02:00:06
Last malicious request observed
Total score reached: 230/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.199.224.179 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

🤖 Bot Detection

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

🔎 Path Enumeration Protection

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

🌊 Traffic Flood Defense

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

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

134.199.224.179 has been assigned a threat score of 230/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:

User-Agent AnomalyPath EnumerationRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 134.199.224.179, geolocated to Santa Clara, United States, operating on the network of DigitalOcean, LLC, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 28 flagged addresses, United States represents a notable presence in our threat database. With a threat score of 230/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly 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

168.144.34.140 (295)167.99.61.194 (270)146.190.116.67 (260)64.227.107.170 (255)165.227.53.4 (245)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

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

💡 Zero-Day Vulnerability Markets

Zero-day vulnerabilities command premium prices in both legitimate and criminal markets. Government agencies, defensive security firms, and criminal organizations compete for these undisclosed flaws, creating a complex ecosystem around vulnerability discovery and disclosure.

🔍 Check Any IP Address

Share this report: