IP Threat Report
104.28.224.67
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Burst 17/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 21/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 5/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| POST seen | Behavioral anomaly detected by automated analysis | +8 | |
| UA changed | Multiple User-Agents — bot rotation technique | +25 |
Observed Activity
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Timeline
Network Provider
Recommendations
Actions taken & recommended
- IP 104.28.224.67 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- 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 104.28.224.67.
🤖 Bot Detection
Address UA spoofing from 104.28.224.67: maintain blocklist of known malicious UA strings, require consistent UA across sessions, implement TLS fingerprinting.
Blacklist Status (DNSBL)
This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.
Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.
Threat Analysis
104.28.224.67 has been assigned a threat score of 213/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:
📊 Threat Analysis
Our monitoring infrastructure has identified 104.28.224.67, geolocated to London, United Kingdom, operating on the network of Cloudflare, Inc., as a source of suspicious network activity. Our sensors captured 490 malicious requests from this address across a 27-day span, reflecting a sustained attack cadence of ~18.1 requests per day. The address operates as a VPN/proxy exit node. Attackers route traffic through anonymizing services to obscure their real location and evade IP-based security controls. The dual attack vectors of Request Flooding combined with User-Agent Anomaly indicate a coordinated assault rather than opportunistic scanning. With a threat score of 213/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Related Threats
🇬🇧 Top threats from United Kingdom
104.28.192.67 (340)104.28.240.58 (305)104.28.192.66 (270)104.28.154.79 (105)View all →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.
💡 Patch Management Urgency
The window between vulnerability disclosure and exploitation continues to shrink. Critical CVEs are now exploited within hours of publication. Automated patch management, virtual patching through WAFs, and rapid deployment pipelines are essential for timely remediation.