ABUSE.MOM
THREAT REPORT

IP Threat Report
172.71.183.175

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-10-25 07:52:18
First seen: 2026-10-06 15:27:54
Last seen: 2026-10-11 01:05:32
160

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHUA_CHANGED
01

Geolocation & Classification

IP Address
172.71.183.175
Type
VPN
Country
🇳🇱 Netherlands
City
Amsterdam
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
132
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 6/2sAbnormally fast request rate — automated scanning+35
Danger strong hits: 1High-risk paths: shells, RCE vectors, exploits+25
Danger strong hits: 4High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 5High-risk paths: shells, RCE vectors, exploits+100
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 285
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-10-06 15:27:54
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 6/2s (+35), Danger strong hits: 1 (+25), Danger strong hits: 4 (+100)
2026-10-11 01:05:32
Last malicious request observed
Total score reached: 160/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cloudflare, Inc.
AS13335 · 🇳🇱 Netherlands

We have detected 710 malicious IPs from this autonomous system.

View all IPs from AS13335 →
06

Recommendations

Actions taken & recommended

  • IP 172.71.183.175 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.183.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.183.175.

🤖 User-Agent Anomaly Defense

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

07

Neighbors in 172.71.183.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
zen.spamhaus.org
✓ Clean
dnsbl.dronebl.org
✓ Clean
bl.blocklist.de
✓ Clean
spam.dnsbl.sorbs.net
✓ Clean
cbl.abuseat.org
✓ Clean
b.barracudacentral.org
✓ Clean
psbl.surriel.com

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

10

Threat Analysis

172.71.183.175 has been assigned a threat score of 160/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.183.175 to malicious activity originating from Amsterdam, Netherlands, operating on the network of Cloudflare, Inc.. The address has been under observation since its initial detection. The address has been active for 4 days in our monitoring system, producing 132 flagged requests at a rate of ~33/day. Classified as a VPN or proxy server, this IP serves as an anonymization layer. While VPNs have legitimate uses, this address has been observed routing clearly malicious traffic. Two attack patterns were identified (Request Flooding and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Netherlands currently accounts for 2,848 blocked IPs in our database, making it a major source of malicious traffic. A score of 160/100 places this address in the top tier of severity. Block and investigate any historical connections.

This IP is associated with a VPN or proxy service. Attackers frequently route their traffic through anonymizing services to obscure their true location. This makes attribution more challenging but the malicious behavior patterns remain detectable.

11

Related Threats

🇳🇱 Top threats from Netherlands

91.92.43.144 (358)91.92.43.186 (358)91.92.43.190 (358)91.92.43.157 (358)91.92.43.153 (358)View all →

🏢 Same network: AS13335

104.28.192.67 (340)104.28.240.58 (305)104.28.205.84 (298)104.28.217.137 (298)104.28.234.181 (288)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.

💡 Brute Force Attack Mechanics

Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.

🔍 Check Any IP Address

Share this report: