ABUSE.MOM
THREAT REPORT

IP Threat Report
5.129.251.15

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 11:20:20
First seen: 2026-04-30 15:00:15
Last seen: 2026-05-04 17:00:04
85

⛔ Verdict: BLOCK

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

RATIO_404BURST
01

Geolocation & Classification

IP Address
5.129.251.15
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
JSC "TIMEWEB"
Organization
JSC "TIMEWEB"
Autonomous System
AS9123 JSC TIMEWEB
Hit Count
42
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 13 req / 10sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 14 req / 10sAbnormally fast request rate — automated scanning+35
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst: 7 req / 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-04-30 15:00:15
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst: 13 req / 2s (+35), Burst: 13 req / 10s (+35)
2026-05-04 17:00:04
Last malicious request observed
Total score reached: 85/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 5.129.251.15 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 5.129.251.15 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Traffic Flood Defense

IP 5.129.251.15 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
zen.spamhaus.org
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

5.129.251.15 has been assigned a threat score of 85/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

Network traffic from 5.129.251.15, located in Moscow, Russia, operating on the network of JSC "TIMEWEB", has been classified as malicious by our automated threat scoring engine. During its 4-day observation window, we recorded 42 hostile requests from this IP — roughly 10.5 per day on average. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With 115 flagged addresses, Russia represents a significant presence in our threat database. The score of 85/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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)72.56.191.6 (265)95.182.125.201 (265)91.240.87.225 (263)View all →

🏢 Same network: AS9123

85.239.41.242 (163)92.53.96.246 (150)185.119.56.182 (140)89.223.120.107 (125)5.129.246.208 (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.

💡 HTTP Header Analysis for Threat Detection

Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.

🔍 Check Any IP Address

Share this report: