ABUSE.MOM
THREAT REPORT

IP Threat Report
204.12.170.245

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 02:20:54
First seen: 2026-06-30 06:13:37
Last seen: 2026-07-05 04:01:36
135

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBE
01

Geolocation & Classification

IP Address
204.12.170.245
Type
Residential
Country
🇺🇸 United States
City
Kansas City
ISP
Nebius Inc.
Organization
Nebius Inc
Autonomous System
AS53428 Nebius Inc.
Hit Count
424
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-06-30 06:13:37
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:36
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.245 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

🔎 Directory Scan Defense

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

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
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
cbl.abuseat.org

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

10

Threat Analysis

204.12.170.245 has been assigned a threat score of 135/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

204.12.170.245 is registered in Kansas City, United States, operating on the network of Nebius Inc.. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Over a period of 4 days, this IP generated 424 malicious requests, averaging approximately 106 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 183 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 135/100 places this address in the top tier of severity. Block and investigate any historical connections.

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

💡 File Upload Vulnerabilities

Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: