ABUSE.MOM
THREAT REPORT

IP Threat Report
204.12.170.213

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 02:20:54
First seen: 2026-07-02 18:35:44
Last seen: 2026-07-05 04:01:42
135

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
204.12.170.213
Type
Residential
Country
🇺🇸 United States
City
Kansas City
ISP
Nebius Inc.
Organization
Nebius Inc
Autonomous System
AS53428 Nebius Inc.
Hit Count
227
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 135
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-07-02 18:35:44
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger strong hits: 4 (+100), Probe 302→404 (+20)
2026-07-05 04:01:42
Last malicious request observed
Total score reached: 135/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Nebius Inc.
AS53428 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

07

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

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

10

Threat Analysis

204.12.170.213 has been assigned a threat score of 135/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Network traffic from 204.12.170.213, located in Kansas City, United States, operating on the network of Nebius Inc., has been classified as malicious by our automated threat scoring engine. The address has been active for 2 days in our monitoring system, producing 227 flagged requests at a rate of ~113.5/day. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 183 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 135/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.214.122 (350)103.168.66.237 (340)34.187.158.4 (340)34.186.187.208 (340)View all →

🏢 Same network: AS53428

204.12.163.33 (135)204.12.188.26 (135)204.12.169.152 (135)204.12.170.225 (135)204.12.188.33 (135)View all →
12

Security Intelligence

💡 API Abuse and Enumeration

Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.

💡 CORS Misconfiguration Exploitation

Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.

🔍 Check Any IP Address

Share this report: