ABUSE.MOM
THREAT REPORT

IP Threat Report
91.210.169.45

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 03:26:03
First seen: 2026-09-14 16:57:55
Last seen: 2026-09-27 01:43:14
183

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404REDIRECT_PROBEREFERERspam
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 10/2sAbnormally fast request rate — automated scanning+35
Burst 11/10sAbnormally fast request rate — automated scanning+35
Burst 11/2sAbnormally fast request rate — automated scanning+35
Burst 12/10sAbnormally fast request rate — automated scanning+35
Burst 12/2sAbnormally fast request rate — automated scanning+35
Burst 13/10sAbnormally fast request rate — automated scanning+35
Burst 13/2sAbnormally fast request rate — automated scanning+35
Burst 14/10sAbnormally fast request rate — automated scanning+35
Burst 14/2sAbnormally fast request rate — automated scanning+35
Burst 15/10sAbnormally fast request rate — automated scanning+35
Burst 15/2sAbnormally fast request rate — automated scanning+35
Burst 16/10sAbnormally fast request rate — automated scanning+35
Burst 16/2sAbnormally fast request rate — automated scanning+35
Burst 17/10sAbnormally fast request rate — automated scanning+35
Burst 17/2sAbnormally fast request rate — automated scanning+35
Burst 18/10sAbnormally fast request rate — automated scanning+35
Burst 18/2sAbnormally fast request rate — automated scanning+35
Burst 19/10sAbnormally fast request rate — automated scanning+35
Burst 20/10sAbnormally fast request rate — automated scanning+35
Burst 20/2sAbnormally fast request rate — automated scanning+35
Burst 21/10sAbnormally fast request rate — automated scanning+35
Burst 21/2sAbnormally fast request rate — automated scanning+35
Burst 22/10sAbnormally fast request rate — automated scanning+35
Burst 23/10sAbnormally fast request rate — automated scanning+35
Burst 24/10sAbnormally fast request rate — automated scanning+35
Burst 24/2sAbnormally fast request rate — automated scanning+35
Burst 25/10sAbnormally fast request rate — automated scanning+35
Burst 25/2sAbnormally fast request rate — automated scanning+35
Burst 26/10sAbnormally fast request rate — automated scanning+35
Burst 27/10sAbnormally fast request rate — automated scanning+35
Burst 28/10sAbnormally fast request rate — automated scanning+35
Burst 29/10sAbnormally fast request rate — automated scanning+35
Burst 29/2sAbnormally fast request rate — automated scanning+35
Burst 30/10sAbnormally fast request rate — automated scanning+35
Burst 31/10sAbnormally fast request rate — automated scanning+35
Burst 32/10sAbnormally fast request rate — automated scanning+35
Burst 33/10sAbnormally fast request rate — automated scanning+35
Burst 35/10sAbnormally fast request rate — automated scanning+35
Burst 36/10sAbnormally fast request rate — automated scanning+35
Burst 37/2sAbnormally fast request rate — automated scanning+35
Burst 40/10sAbnormally fast request rate — automated scanning+35
Burst 44/10sAbnormally fast request rate — automated scanning+35
Burst 45/2sAbnormally fast request rate — automated scanning+35
Burst 5/2sAbnormally fast request rate — automated scanning+35
Burst 59/10sAbnormally fast request rate — automated scanning+35
Burst 6/2sAbnormally fast request rate — automated scanning+35
Burst 7/2sAbnormally fast request rate — automated scanning+35
Burst 8/2sAbnormally fast request rate — automated scanning+35
Burst 9/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 10Medium-risk: admin panels, config files+60
Danger medium hits: 11Medium-risk: admin panels, config files+60
Danger medium hits: 12Medium-risk: admin panels, config files+60
Danger medium hits: 13Medium-risk: admin panels, config files+60
Danger medium hits: 14Medium-risk: admin panels, config files+60
Danger medium hits: 15Medium-risk: admin panels, config files+60
Danger medium hits: 16Medium-risk: admin panels, config files+60
Danger medium hits: 17Medium-risk: admin panels, config files+60
Danger medium hits: 19Medium-risk: admin panels, config files+60
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 21Medium-risk: admin panels, config files+60
Danger medium hits: 22Medium-risk: admin panels, config files+60
Danger medium hits: 25Medium-risk: admin panels, config files+60
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger medium hits: 38Medium-risk: admin panels, config files+60
Danger medium hits: 4Medium-risk: admin panels, config files+40
Danger medium hits: 5Medium-risk: admin panels, config files+50
Danger medium hits: 6Medium-risk: admin panels, config files+60
Danger medium hits: 7Medium-risk: admin panels, config files+60
Danger medium hits: 8Medium-risk: admin panels, config files+60
Danger medium hits: 9Medium-risk: admin panels, config files+60
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
Probe 302→404Behavioral anomaly detected by automated analysis+20
spam:no_js_checkSpam/malware keywords in request content+0
Σ = 2938
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-09-14 16:57:55
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 10/2s (+35), Burst 11/10s (+35)
2026-09-27 01:43:14
Last malicious request observed
Total score reached: 183/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

JSC "TIMEWEB"
AS9123 · 🇷🇺 Russia

We have detected 11 malicious IPs from this autonomous system.

View all IPs from AS9123 →
06

Recommendations

Actions taken & recommended

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

🔎 Path Enumeration Protection

Block scanning from 91.210.169.45: 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 91.210.169.45.

📧 Spam Protection

Enable CAPTCHA on all public forms. Add honeypot fields. Rate-limit submissions to 3 per minute per IP. Deploy Akismet or CleanTalk.

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

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

10

Threat Analysis

91.210.169.45 has been assigned a threat score of 183/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 EnumerationRequest Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 91.210.169.45, geolocated to St Petersburg, Russia, operating on the network of JSC "TIMEWEB", as a source of suspicious network activity. Our sensors captured 9,363 malicious requests from this address across a 12-day span, reflecting a sustained attack cadence of ~780.3 requests per 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. Our records show 2,653 malicious IPs originating from Russia, positioning it as a major contributor to global threat activity. With a threat score of 183/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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.50.25.14 (273)185.103.167.63 (265)View all →

🏢 Same network: AS9123

72.56.238.99 (130)185.114.245.170 (130)5.42.104.209 (120)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.

💡 Race Condition Vulnerabilities

Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.

🔍 Check Any IP Address

Share this report: