ABUSE.MOM
THREAT REPORT

IP Threat Report
5.157.52.164

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-14 17:36:26
First seen: 2026-09-09 04:45:56
Last seen: 2026-09-13 01:12:07
130

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
5.157.52.164
Type
VPN
Country
🇪🇪 EE
City
Tallinn
ISP
Angelnet Limited
Organization
Unknown
Autonomous System
AS57858 Angelnet Limited
Hit Count
144
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Burst 6/2sAbnormally fast request rate — automated scanning+35
Danger medium hits: 5Medium-risk: admin panels, config files+50
Foreign refererReferer from unrelated external domain+10
Probe 302→404Behavioral anomaly detected by automated analysis+20
Σ = 130
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-09 04:45:56
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Burst 6/2s (+35), Danger medium hits: 5 (+50)
2026-09-13 01:12:07
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Angelnet Limited
AS57858 · 🇪🇪 EE
06

Recommendations

Actions taken & recommended

  • IP 5.157.52.164 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 5.157.52.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 5.157.52.164: 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 5.157.52.164.

07

Neighbors in 5.157.52.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
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

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

The address 5.157.52.164 originates from Tallinn, EE, operating on the network of Angelnet Limited. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 3 days in our monitoring system, producing 144 flagged requests at a rate of ~48/day. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. The dual attack vectors of Path Enumeration combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. With a threat score of 130/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇪🇪 Top threats from EE

5.157.52.206 (130)5.157.5.154 (130)5.157.52.22 (130)5.157.52.231 (95)View all →

🏢 Same network: AS57858

196.196.31.196 (165)5.157.0.145 (165)165.231.24.5 (165)196.247.224.35 (130)196.245.186.103 (130)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.

💡 User-Agent Analysis Techniques

Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.

🔍 Check Any IP Address

Share this report: