ABUSE.MOM
THREAT REPORT

IP Threat Report
104.28.234.180

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-09-13 01:26:38
First seen: 2026-08-12 18:14:14
Last seen: 2026-08-16 01:04:06
283

⛔ Verdict: BLOCK

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

BURSTDANGER_PATHMETHODRATIO_404REFERERUA_CHANGEDUA_SUS
01

Geolocation & Classification

IP Address
104.28.234.180
Type
VPN
Country
🇺🇸 United States
City
New York
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
192
02

Detection Signatures

SignatureDescriptionPointsSeverity
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
404 ratio >= 60%Majority of requests returned 404 — enumeration+25
Burst 127/10sAbnormally fast request rate — automated scanning+35
Burst 128/10sAbnormally fast request rate — automated scanning+35
Burst 30/2sAbnormally fast request rate — automated scanning+35
Burst 45/2sAbnormally fast request rate — automated scanning+35
Burst 46/2sAbnormally fast request rate — automated scanning+35
Burst 58/2sAbnormally fast request rate — automated scanning+35
Burst 69/10sAbnormally fast request rate — automated scanning+35
Burst 97/10sAbnormally fast request rate — automated scanning+35
Danger medium hits: 1Medium-risk: admin panels, config files+10
Danger medium hits: 3Medium-risk: admin panels, config files+30
Danger strong hits: 19High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 20High-risk paths: shells, RCE vectors, exploits+100
Danger strong hits: 30High-risk paths: shells, RCE vectors, exploits+100
Foreign refererReferer from unrelated external domain+10
POST seenBehavioral anomaly detected by automated analysis+8
UA changedMultiple User-Agents — bot rotation technique+25
UA suspiciousBehavioral anomaly detected by automated analysis+15
Σ = 718
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-08-12 18:14:14
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
404 ratio 40-60% (+15), 404 ratio >= 60% (+25), Burst 127/10s (+35)
2026-08-16 01:04:06
Last malicious request observed
Total score reached: 283/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cloudflare, Inc.
AS13335 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

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

🔎 Directory Scan Defense

IP 104.28.234.180 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

🌊 Flood / DDoS Mitigation

Implement limit_req_zone in nginx. Deploy CDN with DDoS protection. Configure SYN cookies and connection tracking to throttle 104.28.234.180.

🤖 User-Agent Anomaly Defense

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

07

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

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

10

Threat Analysis

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

Path EnumerationRequest FloodingUser-Agent Anomaly

📊 Threat Analysis

IP address 104.28.234.180 has been traced to New York, United States, operating on the network of Cloudflare, Inc.. Our threat detection systems have flagged this address based on observed malicious behavior patterns. During its 3-day observation window, we recorded 192 hostile requests from this IP — roughly 64 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 50 malicious IPs originating from United States, positioning it as a notable contributor to global threat activity. At 283/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 United States

104.28.205.84 (298)104.28.234.181 (288)104.28.236.175 (280)104.28.251.192 (280)104.28.227.191 (280)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.

💡 False Positive Management

False positives erode trust in security systems and waste analyst resources. Effective management requires feedback loops, allowlisting mechanisms, contextual analysis, and regular tuning of detection rules based on operational experience.

🔍 Check Any IP Address

Share this report: