ABUSE.MOM
THREAT REPORT

IP Threat Report
213.230.87.21

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-29 18:37:52
First seen: 2026-07-17 09:25:59
Last seen: 2026-07-19 04:08:00
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
213.230.87.21
Type
VPN
Country
🇺🇿 UZ
City
Tashkent
ISP
"Uzbektelekom" Joint Stock Company
Organization
Uztelecom
Autonomous System
AS8193 Uzbektelekom Joint Stock Company
Hit Count
121
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Foreign refererReferer from unrelated external domain+10
Σ = 60
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-17 09:25:59
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Danger strong hits: 1 (+25), Foreign referer (+10)
2026-07-19 04:08:00
Last malicious request observed
Total score reached: 60/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

"Uzbektelekom" Joint Stock Company
AS8193 · 🇺🇿 UZ
06

Recommendations

Actions taken & recommended

  • IP 213.230.87.21 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 213.230.87.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 213.230.87.21 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

07

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

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

10

Threat Analysis

213.230.87.21 has been assigned a threat score of 60/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

The address 213.230.87.21 originates from Tashkent, UZ, operating on the network of "Uzbektelekom" Joint Stock Company. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 1-day observation window, we recorded 121 hostile requests from this IP — roughly 121 per day on average. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 71 flagged addresses, UZ represents a notable presence in our threat database. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇺🇿 Top threats from UZ

90.156.195.162 (195)213.230.92.111 (110)213.230.87.96 (103)213.230.87.66 (103)92.253.195.204 (103)View all →

🏢 Same network: AS8193

84.54.71.28 (60)84.54.70.89 (60)213.230.92.36 (60)213.230.116.149 (60)84.54.72.92 (60)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.

💡 Cross-Site Scripting (XSS) Attacks

XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.

🔍 Check Any IP Address

Share this report: