ABUSE.MOM
THREAT REPORT

IP Threat Report
31.173.86.130

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:27:21
First seen: 2026-03-04 12:00:06
Last seen: 2026-03-04 12:00:06
80

⛔ Verdict: BLOCK

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

BURSTREFERER
01

Geolocation & Classification

IP Address
31.173.86.130
Type
Mobile
Country
🇷🇺 Russia
City
Moscow
ISP
MegaFon
Organization
OJSC MegaFon
Autonomous System
AS25159 PJSC MegaFon
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 22 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 22 req / 10sAbnormally fast request rate — automated scanning+35
Foreign referer seenReferer from unrelated external domain+10
Σ = 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-03-04 12:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 22 req / 2s (+35), Burst: 22 req / 10s (+35), Foreign referer seen (+10)
2026-03-04 12:00:06
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

MegaFon
AS25159 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 31.173.86.130 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 31.173.86.0/24
  • 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 31.173.86.130.

07

Neighbors in 31.173.86.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

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

31.173.86.130 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

Network traffic from 31.173.86.130, located in Moscow, Russia, operating on the network of MegaFon, has been classified as malicious by our automated threat scoring engine. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. The address belongs to a mobile carrier network. The sustained pattern of malicious requests indicates either a compromised device or deliberate abuse. Rate-based attacks from this IP aim to overwhelm server resources through high-volume request flooding. Russia currently accounts for 111 blocked IPs in our database, making it a significant source of malicious traffic. 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)72.56.191.6 (265)95.182.125.201 (265)91.240.87.225 (263)View all →

🏢 Same network: AS25159

94.25.172.198 (140)178.176.78.240 (90)31.173.86.253 (80)178.176.74.78 (80)31.173.80.186 (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.

💡 XML External Entity (XXE) Attacks

XXE vulnerabilities in XML parsers allow attackers to read local files, perform SSRF, and execute denial of service attacks. Many legacy applications and APIs remain vulnerable to XXE due to insecure default XML parser configurations.

🔍 Check Any IP Address

Share this report: