ABUSE.MOM
THREAT REPORT

IP Threat Report
5.157.5.99

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 07:53:31
First seen: 2026-05-01 22:00:06
Last seen: 2026-05-01 22:00:06
85

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
5.157.5.99
Type
Residential
Country
🇪🇪 EE
City
Tallinn
ISP
Interconnects
Organization
Unknown
Autonomous System
AS57858 Angelnet Limited
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 4Medium-risk: admin panels, config files+40
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Σ = 85
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-05-01 22:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 4 (+40), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-05-01 22:00:06
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

Interconnects
AS57858 · 🇪🇪 EE
06

Recommendations

Actions taken & recommended

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

07

Neighbors in 5.157.5.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (4)
PortServiceRiskDescription
80HTTPLowHTTP web server — standard web traffic
4444UnknownLowService on port 4444
7777UnknownLowService on port 7777
12345UnknownLowService on port 12345

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

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
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com
✓ Clean
dnsbl-1.uceprotect.net

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

10

Threat Analysis

5.157.5.99 has been assigned a threat score of 85/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Our monitoring infrastructure has identified 5.157.5.99, geolocated to Tallinn, EE, operating on the network of Interconnects, as a source of suspicious network activity. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. At 85/100, this IP warrants immediate defensive action.

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 EE

5.157.5.149 (150)5.157.5.62 (140)5.157.5.129 (140)5.34.240.185 (140)5.157.5.122 (120)View all →

🏢 Same network: AS57858

151.237.187.135 (220)5.157.5.149 (150)5.157.20.73 (140)5.157.20.26 (140)5.157.5.62 (140)View all →
12

Security Intelligence

💡 WordPress-Specific Attack Vectors

WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.

💡 VPN Exit Node Reputation

VPN exit nodes aggregate traffic from many users, creating mixed reputation profiles. While legitimate users seek privacy, attackers exploit VPN services to anonymize malicious activity, making IP-based blocking of VPN nodes a complex policy decision.

🔍 Check Any IP Address

Share this report: