ABUSE.MOM
THREAT REPORT

IP Threat Report
84.54.72.73

ABUSE.MOM — BEHAVE OR GET EXPOSED

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

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REFERER
01

Geolocation & Classification

IP Address
84.54.72.73
Type
Residential
Country
🇺🇿 UZ
City
Toshbuloq
ISP
"Uzbektelekom" Joint Stock Company
Organization
Uztelecom
Autonomous System
AS8193 Uzbektelekom Joint Stock Company
Hit Count
72
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-22 18:00:16
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:21
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

We have detected 64 malicious IPs from this autonomous system.

View all IPs from AS8193 →
06

Recommendations

Actions taken & recommended

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

07

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

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

10

Threat Analysis

84.54.72.73 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

Network traffic from 84.54.72.73, located in Toshbuloq, UZ, operating on the network of "Uzbektelekom" Joint Stock Company, has been classified as malicious by our automated threat scoring engine. During its 2-day observation window, we recorded 72 hostile requests from this IP — roughly 36 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. UZ currently accounts for 84 blocked IPs in our database, making it a notable source of malicious traffic. At 60/100, this IP presents a meaningful threat. Implement rate limiting with escalation to blocking.

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 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: AS8193

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

Security Intelligence

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 Botnet Command and Control Evolution

Botnet C2 infrastructure has evolved from centralized IRC channels to resilient peer-to-peer networks, domain generation algorithms, and blockchain-based communication. This evolution makes botnet takedowns increasingly difficult and expensive.

🔍 Check Any IP Address

Share this report: