ABUSE.MOM
THREAT REPORT

IP Threat Report
188.113.235.69

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 16:21:22
First seen: 2026-10-20 18:28:02
Last seen: 2026-10-25 04:04:10
60

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
188.113.235.69
Type
Mobile
Country
🇺🇿 UZ
City
Tashkent
ISP
Ucell
Organization
Unknown
Autonomous System
AS49273 COSCOM Liability Limited Company
Hit Count
97
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-10-20 18:28:02
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-10-25 04:04:10
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

Ucell
AS49273 · 🇺🇿 UZ

We have detected 4 malicious IPs from this autonomous system.

View all IPs from AS49273 →
06

Recommendations

Actions taken & recommended

  • IP 188.113.235.69 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

🔎 Directory Scan Defense

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

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

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

10

Threat Analysis

188.113.235.69 has been assigned a threat score of 60/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 188.113.235.69, geolocated to Tashkent, UZ, operating on the network of Ucell, as a source of suspicious network activity. During its 4-day observation window, we recorded 97 hostile requests from this IP — roughly 24.3 per day on average. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 84 malicious IPs originating from UZ, positioning it as a notable contributor to global threat activity. The score of 60/100 warrants active monitoring and rate-limiting. Full blocking is advisable for sensitive systems.

11

Related Threats

🇺🇿 Top threats from UZ

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

🏢 Same network: AS49273

188.113.251.116 (70)188.113.206.34 (60)188.113.245.23 (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.

💡 Passive DNS for Threat Hunting

Passive DNS databases record historical DNS resolution data, enabling analysts to track domain changes, identify related infrastructure, and discover malicious domains sharing hosting with known threats. This historical context is invaluable for threat investigation.

🔍 Check Any IP Address

Share this report: