ABUSE.MOM
THREAT REPORT

IP Threat Report
92.36.103.169

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 11:40:06
First seen: 2026-02-17 17:25:07
Last seen: 2026-02-17 17:26:16
80

⛔ Verdict: BLOCK

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

BURSTREFERERIMPORT
01

Geolocation & Classification

IP Address
92.36.103.169
Type
Mobile
Country
🇷🇺 Russia
City
Moscow
ISP
T2 Russia Groups
Organization
Unknown
Autonomous System
AS12958 T2 Mobile LLC
Hit Count
3
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 21 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 21 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Imported from old blocklistBehavioral anomaly detected by automated analysis+0
Σ = 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-02-17 17:25:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 21 req / 2s (+35), Burst: 21 req / 10s (+35), Foreign referer seen (+10)
2026-02-17 17:26:16
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

T2 Russia Groups
AS12958 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

IP 92.36.103.169 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

09

Blacklist Status (DNSBL)

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

⛔ LISTED
Spamhaus ZEN

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

10

Threat Analysis

92.36.103.169 has been assigned a threat score of 80/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:

Request Flooding

📊 Threat Analysis

Our monitoring infrastructure has identified 92.36.103.169, geolocated to Moscow, Russia, operating on the network of T2 Russia Groups, as a source of suspicious network activity. During its 1-day observation window, we recorded 3 hostile requests from this IP — roughly 3 per day on average. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 102 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. A threat score of 80/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.

11

Related Threats

🇷🇺 Top threats from Russia

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

🏢 Same network: AS12958

92.36.52.166 (80)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.

💡 Backup and Recovery Against Ransomware

Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.

🔍 Check Any IP Address

Share this report: