ABUSE.MOM
THREAT REPORT

IP Threat Report
46.138.250.165

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-26 05:17:56
First seen: 2026-07-15 05:44:05
Last seen: 2026-07-26 04:01:26
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 15/10sAbnormally fast request rate — automated scanning+35
Burst 15/2sAbnormally fast request rate — automated scanning+35
Burst 6/2sAbnormally fast request rate — automated scanning+35
Foreign refererReferer from unrelated external domain+10
Σ = 115
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-07-15 05:44:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 15/10s (+35), Burst 15/2s (+35), Burst 6/2s (+35)
2026-07-26 04:01:26
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

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

Recommendations

Actions taken & recommended

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

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 46.138.250.165.

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
spam.dnsbl.sorbs.net
✓ Clean
dnsbl.dronebl.org

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

10

Threat Analysis

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

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

IP address 46.138.250.165 has been traced to Moscow, Russia, operating on the network of Moscow Local Telephone Network (PJSC MGTS). Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 10 days in our monitoring system, producing 464 flagged requests at a rate of ~46.4/day. This is a mobile network IP. While mobile addresses are typically shared via CGNAT, persistent malicious activity from this specific address suggests automated abuse. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Our records show 102 malicious IPs originating from Russia, 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.

11

Related Threats

🇷🇺 Top threats from Russia

157.22.102.172 (313)178.130.54.159 (288)185.103.167.63 (265)72.56.191.6 (265)95.182.125.201 (265)View all →

🏢 Same network: AS25513

79.139.240.2 (70)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.

💡 Command Injection Techniques

Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.

🔍 Check Any IP Address

Share this report: