ABUSE.MOM
THREAT REPORT

IP Threat Report
92.53.96.201

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-11 02:09:11
First seen: 2026-10-01 17:58:45
Last seen: 2026-10-11 01:06:52
95

⛔ Verdict: BLOCK

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

BURSTRATIO_404
01

Geolocation & Classification

IP Address
92.53.96.201
Type
Hosting
Country
🇷🇺 Russia
City
St Petersburg
ISP
JSC "TIMEWEB"
Organization
JSC "TIMEWEB"
Autonomous System
AS9123 JSC TIMEWEB
Hit Count
1744
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 27/10sAbnormally fast request rate — automated scanning+35
Burst 27/2sAbnormally fast request rate — automated scanning+35
Burst 5/2sAbnormally fast request rate — automated scanning+35
Burst 50/10sAbnormally fast request rate — automated scanning+35
Burst 50/2sAbnormally fast request rate — automated scanning+35
Σ = 215
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
[redacted]
GET
/page
200
Requests shown: 2 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-10-01 17:58:45
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 27/10s (+35)
2026-10-11 01:06:52
Last malicious request observed
Total score reached: 95/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

JSC "TIMEWEB"
AS9123 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 92.53.96.201.

07

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

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

10

Threat Analysis

92.53.96.201 has been assigned a threat score of 95/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

92.53.96.201 is registered in St Petersburg, Russia, operating on the network of JSC "TIMEWEB". This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. The address has been active for 9 days in our monitoring system, producing 1,744 flagged requests at a rate of ~193.8/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Russia currently accounts for 111 blocked IPs in our database, making it a significant source of malicious traffic. At 95/100, this is an extremely high-risk address. All traffic should be considered hostile.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

11

Related Threats

🇷🇺 Top threats from Russia

157.22.102.172 (313)178.130.54.159 (288)213.183.54.30 (275)185.103.167.63 (265)72.56.191.6 (265)View all →

🏢 Same network: AS9123

91.210.169.45 (183)72.56.238.99 (130)185.114.245.170 (130)185.104.114.127 (95)201.34.128.48 (95)View all →
12

Security Intelligence

💡 DDoS Mitigation Approaches

Distributed denial of service attacks overwhelm infrastructure with traffic volume. Effective mitigation combines always-on traffic scrubbing, anycast network distribution, rate limiting, and the ability to quickly scale absorption capacity during attacks.

💡 Digital Forensics Fundamentals

Digital forensics preserves and analyzes electronic evidence following attacks. Proper chain of custody, forensic imaging, timeline reconstruction, and artifact analysis are essential for understanding attack scope, attribution, and preventing recurrence.

🔍 Check Any IP Address

Share this report: