ABUSE.MOM
THREAT REPORT

IP Threat Report
172.71.184.232

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 06:55:34
First seen: 2026-04-14 10:00:06
Last seen: 2026-05-16 08:00:06
130

⛔ Verdict: BLOCK

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

DANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
172.71.184.232
Type
Hosting
Country
🇷🇺 Russia
City
Moscow
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
4
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger medium hits: 1Medium-risk: admin panels, config files+10
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Danger strong hits: 3High-risk paths: shells, RCE vectors, exploits+75
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 2Medium-risk: admin panels, config files+20
Σ = 235
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-04-14 10:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 1 (+25), Danger medium hits: 1 (+10), UA changed for same IP (+25)
2026-05-16 08:00:06
Last malicious request observed
Total score reached: 130/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cloudflare, Inc.
AS13335 · 🇷🇺 Russia
06

Recommendations

Actions taken & recommended

  • IP 172.71.184.232 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 172.71.184.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🤖 Bot Detection

Address UA spoofing from 172.71.184.232: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.

07

Neighbors in 172.71.184.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
zen.spamhaus.org
✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

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

User-Agent Anomaly

📊 Threat Analysis

Network traffic from 172.71.184.232, located in Moscow, Russia, operating on the network of Cloudflare, Inc., has been classified as malicious by our automated threat scoring engine. During its 31-day observation window, we recorded 4 hostile requests from this IP — roughly 0.1 per day on average. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. The IP exhibits User-Agent manipulation, switching between different browser identities or sending empty headers. Our records show 128 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. A score of 130/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP belongs to a hosting or data center provider. Malicious traffic from hosting infrastructure often originates from compromised VPS instances, rented servers used for scanning campaigns, or abused free-tier cloud accounts. Hosting providers typically respond to abuse reports within 24-72 hours.

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: AS13335

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →
12

Security Intelligence

💡 HTTP Request Smuggling

Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.

💡 Cryptojacking Detection and Prevention

Cryptojacking hijacks computing resources to mine cryptocurrency without consent. Indicators include unusual CPU usage, specific network connections to mining pools, and JavaScript miners embedded in compromised websites. Server-side cryptojacking can persist undetected for months.

🔍 Check Any IP Address

Share this report: