ABUSE.MOM
THREAT REPORT

IP Threat Report
172.71.184.16

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 09:10:00
First seen: 2026-05-13 07:00:07
Last seen: 2026-05-13 07:00:07
75

⛔ Verdict: BLOCK

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

DANGER_PATHRATIO_404
01

Geolocation & Classification

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

Detection Signatures

SignatureDescriptionPointsSeverity
Danger strong hits: 2High-risk paths: shells, RCE vectors, exploits+50
Danger medium hits: 1Medium-risk: admin panels, config files+10
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Σ = 75
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-05-13 07:00:07
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger strong hits: 2 (+50), Danger medium hits: 1 (+10), 404 ratio 40-60% (+15)
2026-05-13 07:00:07
Last malicious request observed
Total score reached: 75/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.16 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

🔎 Path Enumeration Protection

Block scanning from 172.71.184.16: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.

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.

✓ Clean
ix.dnsbl.manitu.net
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl.sorbs.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
zen.spamhaus.org
✓ 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.16 has been assigned a threat score of 75/100 (High). The IP is rated as a high-level threat. Network administrators should implement blocking rules and monitor for any connections from this address.

The following attack categories were identified:

Path Enumeration

📊 Threat Analysis

Network traffic from 172.71.184.16, located in Moscow, Russia, operating on the network of Cloudflare, Inc., has been classified as malicious by our automated threat scoring engine. Our sensors captured 1 malicious requests from this address across a 1-day span, reflecting a sustained attack cadence of ~1 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. Our records show 128 malicious IPs originating from Russia, positioning it as a significant contributor to global threat activity. The score of 75/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.

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

💡 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.

💡 Phishing Infrastructure Analysis

Modern phishing operations use sophisticated infrastructure including lookalike domains, valid TLS certificates, and evasion techniques like cloaking and geofencing. Analyzing this infrastructure reveals campaigns before they reach their targets.

🔍 Check Any IP Address

Share this report: