ABUSE.MOM
THREAT REPORT

IP Threat Report
31.173.80.186

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 06:27:21
First seen: 2026-02-24 18:00:05
Last seen: 2026-02-24 18:00:05
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.80.186
Type
Mobile
Country
🇷🇺 Russia
City
Moscow
ISP
MegaFon
Organization
OJSC MegaFon
Autonomous System
AS25159 PJSC MegaFon
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 13 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 14 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-02-24 18:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 13 req / 2s (+35), Burst: 14 req / 10s (+35), Foreign referer seen (+10)
2026-02-24 18:00:05
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.80.186 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.80.0/24
  • 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 31.173.80.186 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

07

Neighbors in 31.173.80.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.80.186 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

Network traffic from 31.173.80.186, located in Moscow, Russia, operating on the network of MegaFon, has been classified as malicious by our automated threat scoring engine. The address has been active for 1 days in our monitoring system, producing 1 flagged requests at a rate of ~1/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. The IP is engaged in request flooding, sending traffic at rates designed to exhaust server capacity. Our records show 111 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. At 80/100, this IP warrants immediate defensive action.

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)94.25.168.167 (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.

💡 IoT Device Compromise Patterns

Internet of Things devices are prime targets for botnet recruitment due to weak default credentials, infrequent updates, and always-on connectivity. Compromised IoT devices generate persistent scanning and attack traffic without their owners knowledge.

🔍 Check Any IP Address

Share this report: