ABUSE.MOM
THREAT REPORT

IP Threat Report
165.227.12.158

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 09:14:26
First seen: 2026-05-25 06:16:28
Last seen: 2026-05-30 09:05:15
120

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEUA_SUS
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Probe 302→404Behavioral anomaly detected by automated analysis+20
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 120
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-05-25 06:16:28
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 2 (+20), Danger strong hits: 2 (+50)
2026-05-30 09:05:15
Last malicious request observed
Total score reached: 120/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 165.227.12.158 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

🔎 Path Enumeration Protection

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

🤖 Bot Detection

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

09

Blacklist Status (DNSBL)

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

✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
zen.spamhaus.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

165.227.12.158 has been assigned a threat score of 120/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

The address 165.227.12.158 originates from Santa Clara, United States, operating on the network of DigitalOcean, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 5 days in our monitoring system, producing 1,099 flagged requests at a rate of ~219.8/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 128 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 120/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

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

💡 VPN Exit Node Reputation

VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.

🔍 Check Any IP Address

Share this report: