ABUSE.MOM
THREAT REPORT

IP Threat Report
109.252.156.24

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 15:00:19
First seen: 2026-05-18 21:12:08
Last seen: 2026-05-24 09:42:20
98

⛔ Verdict: BLOCK

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

DANGER_PATHMETHODRATIO_404REFERERUA_CHANGED
01

Geolocation & Classification

IP Address
109.252.156.24
Type
Residential
Country
🇷🇺 Russia
City
Moscow
ISP
Moscow Local Telephone Network (OAO MGTS)
Organization
OAO Mgts)
Autonomous System
AS25513 PJSC Moscow city telephone network
Hit Count
297
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger medium hits: 4Medium-risk: admin panels, config files+40
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 118
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-18 21:12:08
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), Danger medium hits: 2 (+20), Danger medium hits: 4 (+40)
2026-05-24 09:42:20
Last malicious request observed
Total score reached: 98/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Moscow Local Telephone Network (OAO MGTS)
AS25513 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

Address UA spoofing from 109.252.156.24: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

09

Blacklist Status (DNSBL)

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

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

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

10

Threat Analysis

109.252.156.24 has been assigned a threat score of 98/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.

The following attack categories were identified:

Path EnumerationUser-Agent Anomaly

📊 Threat Analysis

IP address 109.252.156.24 has been traced to Moscow, Russia, operating on the network of Moscow Local Telephone Network (OAO MGTS). Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 297 malicious requests from this address across a 5-day span, reflecting a sustained attack cadence of ~59.4 requests per 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. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Russia currently accounts for 122 blocked IPs in our database, making it a significant source of malicious traffic. A score of 98/100 places this address in the top tier of severity. Block and investigate any historical connections.

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 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: AS25513

109.252.168.207 (138)109.252.150.101 (138)109.252.175.246 (133)109.252.158.136 (118)46.138.3.210 (113)View all →
12

Security Intelligence

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

💡 Mobile Network Threat Landscape

Mobile carrier NAT (CGNAT) means thousands of users share a single public IP, making mobile IPs unreliable for reputation scoring. However, mobile networks are increasingly used as attack platforms through compromised apps and malicious SDKs.

🔍 Check Any IP Address

Share this report: