ABUSE.MOM
THREAT REPORT

IP Threat Report
109.248.170.2

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 08:45:17
First seen: 2026-09-23 10:50:02
Last seen: 2026-10-25 04:06:10
80

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHRATIO_404
01

Geolocation & Classification

IP Address
109.248.170.2
Type
Hosting
Country
🇰🇿 KZ
City
Karaganda
ISP
PE Fedinyak Sergey Vyacheslavovich
Organization
PE Fedinyak Sergey Vyacheslavovich
Autonomous System
AS203087 Fedinyak Sergey Vyacheslavovich
Hit Count
654
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 11/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 2Medium-risk: admin panels, config files+20
Σ = 80
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-23 10:50:02
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio >= 60% (+25), Burst 11/10s (+35), Danger medium hits: 2 (+20)
2026-10-25 04:06:10
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

PE Fedinyak Sergey Vyacheslavovich
AS203087 · 🇰🇿 KZ
06

Recommendations

Actions taken & recommended

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

09

Blacklist Status (DNSBL)

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

✓ Clean
b.barracudacentral.org
✓ Clean
bl.blocklist.de
✓ Clean
psbl.surriel.com
✓ Clean
cbl.abuseat.org
✓ Clean
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

109.248.170.2 has been assigned a threat score of 80/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Path EnumerationRequest Flooding

📊 Threat Analysis

109.248.170.2 is registered in Karaganda, KZ, operating on the network of PE Fedinyak Sergey Vyacheslavovich. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 654 malicious requests from this address across a 31-day span, reflecting a sustained attack cadence of ~21.1 requests per day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 157 malicious IPs originating from KZ, positioning it as a significant contributor to global threat activity. The score of 80/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 KZ

173.239.196.75 (255)173.239.196.79 (255)173.239.196.73 (255)173.239.196.71 (255)173.239.196.67 (255)View all →

🏢 Same network: AS203087

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.

💡 Content Delivery Network Risks

CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.

🔍 Check Any IP Address

Share this report: