ABUSE.MOM
THREAT REPORT

IP Threat Report
46.138.209.116

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-26 04:49:36
First seen: 2026-09-09 12:45:00
Last seen: 2026-09-13 01:13:41
85

⛔ Verdict: BLOCK

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

DANGER_PATHREFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Foreign refererReferer 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-09-09 12:45:00
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 3 (+75), Foreign referer (+10)
2026-09-13 01:13:41
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

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

We have detected 36 malicious IPs from this autonomous system.

View all IPs from AS25513 →
06

Recommendations

Actions taken & recommended

  • IP 46.138.209.116 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

⚙️ Defensive Recommendations

Block 46.138.209.116 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.

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
zen.spamhaus.org
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
bl.blocklist.de
✓ Clean
cbl.abuseat.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

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

📊 Threat Analysis

Threat intelligence analysis has linked 46.138.209.116 to malicious activity originating from Moscow, Russia, operating on the network of Moscow Local Telephone Network (PJSC MGTS). The address has been under observation since its initial detection. During its 3-day observation window, we recorded 102 hostile requests from this IP — roughly 34 per day on average. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. With 2,648 flagged addresses, Russia represents a major presence in our threat database. 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 Russia

157.22.102.172 (313)178.130.54.159 (288)213.183.54.30 (275)185.50.25.14 (273)185.103.167.63 (265)View all →

🏢 Same network: AS25513

109.252.168.207 (138)109.252.150.101 (138)109.252.175.246 (133)109.252.170.202 (130)109.252.158.136 (118)View all →
12

Security Intelligence

💡 Prototype Pollution Attacks

Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.

💡 Edge Computing Attack Surface

Edge computing pushes processing closer to users but expands the attack surface. Edge nodes often run in less secure environments than centralized data centers, creating new opportunities for physical access attacks and supply chain compromises.

🔍 Check Any IP Address

Share this report: