ABUSE.MOM
THREAT REPORT

IP Threat Report
104.28.217.139

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-07-30 01:42:39
First seen: 2026-07-21 12:44:25
Last seen: 2026-07-26 04:01:24
253

⛔ Verdict: BLOCK

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

BOT_UABURSTDANGER_PATHMETHODREFERERUA_CHANGED
01

Geolocation & Classification

IP Address
104.28.217.139
Type
VPN
Country
🇳🇱 Netherlands
City
Utrecht
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
291
02

Detection Signatures

SignatureDescriptionPointsSeverity
Burst 28/2sAbnormally fast request rate — automated scanning+35
Burst 56/10sAbnormally fast request rate — automated scanning+35
Danger strong hits: 33High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA bot: Go-http-clientKnown bot/crawler User-Agent detected+40
UA changedMultiple User-Agents — bot rotation technique+25
Σ = 253
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-07-21 12:44:25
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Burst 28/2s (+35), Burst 56/10s (+35), Danger strong hits: 33 (+100)
2026-07-26 04:01:24
Last malicious request observed
Total score reached: 253/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cloudflare, Inc.
AS13335 · 🇳🇱 Netherlands
06

Recommendations

Actions taken & recommended

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

🌊 Traffic Flood Defense

IP 104.28.217.139 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.

🤖 Bot Detection

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

07

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

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

10

Threat Analysis

104.28.217.139 has been assigned a threat score of 253/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.

The following attack categories were identified:

Request FloodingUser-Agent Anomaly

📊 Threat Analysis

Our monitoring infrastructure has identified 104.28.217.139, geolocated to Utrecht, Netherlands, operating on the network of Cloudflare, Inc., as a source of suspicious network activity. During its 4-day observation window, we recorded 291 hostile requests from this IP — roughly 72.8 per day on average. 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. At 253/100, this is an extremely high-risk address. All traffic should be considered hostile.

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

104.28.217.137 (298)104.28.155.237 (195)104.28.163.193 (135)104.28.158.29 (120)104.28.30.75 (105)View all →

🏢 Same network: AS13335

104.28.217.137 (298)104.28.236.175 (280)104.28.205.83 (268)104.28.236.176 (253)104.28.243.188 (253)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.

💡 Race Condition Vulnerabilities

Race conditions occur when application behavior depends on the timing of concurrent operations. Attackers exploit these timing windows to bypass limits, duplicate transactions, or escalate privileges by sending carefully timed parallel requests.

🔍 Check Any IP Address

Share this report: