ABUSE.MOM
THREAT REPORT

IP Threat Report
104.28.159.129

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-27 09:02:23
First seen: 2026-05-06 00:00:06
Last seen: 2026-05-12 19:00:07
80

⛔ Verdict: BLOCK

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

UA_CHANGEDREFERERDANGER_PATHBURST
01

Geolocation & Classification

IP Address
104.28.159.129
Type
Hosting
Country
🇸🇬 Singapore
City
Singapore
ISP
Cloudflare, Inc.
Organization
Cloudflare WARP
Autonomous System
AS13335 Cloudflare, Inc.
Hit Count
4
02

Detection Signatures

SignatureDescriptionPointsSeverity
UA changed for same IPMultiple User-Agents — bot rotation technique+25
Foreign referer seenReferer from unrelated external domain+10
Danger medium hits: 2Medium-risk: admin panels, config files+20
Burst: 5 req / 2sAbnormally fast request rate — automated scanning+35
Burst: 6 req / 2sAbnormally fast request rate — automated scanning+35
Σ = 125
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-05-06 00:00:06
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
UA changed for same IP (+25), Foreign referer seen (+10), Danger medium hits: 2 (+20)
2026-05-12 19:00:07
Last malicious request observed
Total score reached: 80/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

Cloudflare, Inc.
AS13335 · 🇸🇬 Singapore
06

Recommendations

Actions taken & recommended

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

🤖 Bot Detection

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

🌊 Flood / DDoS Mitigation

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

07

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

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

10

Threat Analysis

104.28.159.129 has been assigned a threat score of 80/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.

The following attack categories were identified:

User-Agent AnomalyRequest Flooding

📊 Threat Analysis

The address 104.28.159.129 originates from Singapore, Singapore, operating on the network of Cloudflare, Inc.. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 4 malicious requests from this address across a 6-day span, reflecting a sustained attack cadence of ~0.7 requests per day. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of User-Agent Anomaly combined with Request Flooding indicate a coordinated assault rather than opportunistic scanning. Our records show 26 malicious IPs originating from Singapore, positioning it as a notable contributor to global threat activity. At 80/100, this IP warrants immediate defensive action.

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 Singapore

104.28.156.135 (268)104.28.159.48 (268)104.28.156.151 (268)104.28.156.138 (240)104.28.159.50 (240)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

💡 TLS Fingerprinting (JA3/JA4)

TLS fingerprinting creates unique identifiers based on how clients negotiate encrypted connections. The JA3 and JA4 methods generate hashes from TLS ClientHello parameters, enabling identification of specific tools and malware regardless of IP address changes.

💡 TLS Certificate Misconfigurations

Expired, self-signed, or misconfigured TLS certificates create security vulnerabilities and trust issues. Certificate monitoring, automated renewal through ACME protocols, and proper certificate chain configuration prevent both security gaps and service disruptions.

🔍 Check Any IP Address

Share this report: