ABUSE.MOM
THREAT REPORT

IP Threat Report
172.71.172.168

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-30 12:49:16
First seen: 2026-03-30 14:00:04
Last seen: 2026-05-24 10:21:07
205

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATHUA_SUS
01

Geolocation & Classification

IP Address
172.71.172.168
Type
Hosting
Country
🇩🇪 Germany
City
Frankfurt
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
67
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst: 20 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 23 req / 10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 2Medium-risk: admin panels, config files+20
Danger strong hits: 22High-risk paths: shells, RCE vectors, exploits+100
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA suspicious (short/empty)Behavioral anomaly detected by automated analysis+15
Σ = 245
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-30 14:00:04
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst: 20 req / 2s (+35), Burst: 23 req / 10s (+35), Danger medium hits: 2 (+20)
2026-05-24 10:21:07
Last malicious request observed
Total score reached: 205/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cloudflare, Inc.
AS13335 · 🇩🇪 Germany
06

Recommendations

Actions taken & recommended

  • IP 172.71.172.168 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.172.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 172.71.172.168.

🤖 User-Agent Anomaly Defense

IP 172.71.172.168 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.

07

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

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

10

Threat Analysis

172.71.172.168 has been assigned a threat score of 205/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Threat intelligence analysis has linked 172.71.172.168 to malicious activity originating from Frankfurt, Germany, operating on the network of Cloudflare, Inc.. The address has been under observation since its initial detection. During its 54-day observation window, we recorded 67 hostile requests from this IP — roughly 1.2 per day on average. 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. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. With 197 flagged addresses, Germany represents a significant presence in our threat database. A score of 205/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 Germany

15.220.152.241 (320)77.81.65.244 (313)185.168.29.98 (313)91.217.249.222 (305)212.30.36.219 (305)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

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

💡 Initial Access Broker Marketplace

Initial access brokers specialize in gaining entry to corporate networks and selling that access to ransomware operators. This specialization creates an efficient criminal marketplace where compromised credentials and VPN access are traded as commodities.

🔍 Check Any IP Address

Share this report: