ABUSE.MOM
THREAT REPORT

IP Threat Report
128.71.123.122

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 04:29:51
First seen: 2026-03-01 07:00:06
Last seen: 2026-03-01 07: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
128.71.123.122
Type
Mobile
Country
🇷🇺 Russia
City
Moscow
ISP
16345 Mobile Region
Organization
Unknown
Autonomous System
AS16345 PJSC "Vimpelcom"
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 14 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
Σ = 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-01 07:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 14 req / 2s (+35), Burst: 21 req / 10s (+35), Foreign referer seen (+10)
2026-03-01 07: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

16345 Mobile Region
AS16345 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 128.71.123.122 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 128.71.123.122.

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

128.71.123.122 has been assigned a threat score of 80/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.

The following attack categories were identified:

Request Flooding

📊 Threat Analysis

128.71.123.122 is registered in Moscow, Russia, operating on the network of 16345 Mobile Region. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per 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. Russia currently accounts for 108 blocked IPs in our database, making it a significant source of malicious traffic. 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: AS16345

128.71.9.141 (120)128.71.179.119 (93)128.71.193.13 (85)128.71.33.63 (80)217.118.83.177 (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.

💡 Subnet-Level vs IP-Level Blocking

When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.

🔍 Check Any IP Address

Share this report: