ABUSE.MOM
THREAT REPORT

IP Threat Report
94.124.162.26

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:46:49
First seen: 2026-03-11 00:00:09
Last seen: 2026-03-19 03:00:06
103

⛔ Verdict: BLOCK

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

DANGER_PATHMETHOD
01

Geolocation & Classification

IP Address
94.124.162.26
Type
Residential
Country
🇺🇦 Ukraine
City
Kharkiv
ISP
Therecom Ltd
Organization
Bilberry
Autonomous System
AS56465 Therecom Ltd
Hit Count
2
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 2Medium-risk: admin panels, config files+20
POST requests presentBehavioral anomaly detected by automated analysis+8
Σ = 103
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-03-11 00:00:09
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Danger medium hits: 2 (+20), POST requests present (+8)
2026-03-19 03:00:06
Last malicious request observed
Total score reached: 103/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Therecom Ltd
AS56465 · 🇺🇦 Ukraine
06

Recommendations

Actions taken & recommended

  • IP 94.124.162.26 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 94.124.162.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

⚙️ General Security

Add 94.124.162.26 to your firewall blocklist. Review logs for successful connections. Enable comprehensive logging on all public-facing services.

07

Neighbors in 94.124.162.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
Spamhaus ZEN

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

10

Threat Analysis

94.124.162.26 has been assigned a threat score of 103/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

📊 Threat Analysis

The address 94.124.162.26 originates from Kharkiv, Ukraine, operating on the network of Therecom Ltd. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 8 days in our monitoring system, producing 2 flagged requests at a rate of ~0.3/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Ukraine currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. With a threat score of 103/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.

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 Ukraine

104.28.230.33 (165)195.66.105.234 (165)104.28.156.60 (165)193.93.230.171 (165)85.137.53.159 (155)View all →

🏢 Same network: AS56465

94.124.162.12 (103)View all →
12

Security Intelligence

💡 Server-Side Request Forgery (SSRF)

SSRF attacks trick servers into making requests to internal resources that should not be publicly accessible. This can expose cloud metadata endpoints, internal APIs, and private network services, potentially leading to full infrastructure compromise.

💡 Security Header Best Practices

HTTP security headers provide defense-in-depth with minimal implementation effort. Key headers include Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, and Permissions-Policy, each addressing specific attack vectors.

🔍 Check Any IP Address

Share this report: