IP Threat Report
104.209.144.33
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +25 | |
| Burst 12/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 14/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 16/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 18/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 19/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 20/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 21/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 22/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 23/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 24/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 25/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 48/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 61/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 62/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 63/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 64/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 66/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 67/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 68/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 71/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 72/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 74/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 75/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 76/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 77/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 78/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 79/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 80/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 81/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 82/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 83/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 84/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 85/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 86/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 87/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 88/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 89/10s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 100 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 150 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 176 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 177 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 197 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 198 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 199 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 203 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 208 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 209 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 224 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 229 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 298 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 308 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 312 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 313 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 328 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 329 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 352 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 430 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 48 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 532 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 596 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 75 | Medium-risk: admin panels, config files | +60 | |
| Danger strong hits: 1 | High-risk paths: shells, RCE vectors, exploits | +25 | |
| Danger strong hits: 100 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 12 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 123 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 140 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 142 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 156 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 210 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 24 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 25 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 28 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 280 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 282 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger strong hits: 33 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 42 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 50 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 52 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 56 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 560 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 6 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 70 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 75 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 78 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 82 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| UA suspicious | Behavioral anomaly detected by automated analysis | +15 |
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.209.144.33 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
🔎 Path Enumeration Protection
Block scanning from 104.209.144.33: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 104.209.144.33 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
🤖 User-Agent Anomaly Defense
IP 104.209.144.33 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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.209.144.33 has been assigned a threat score of 280/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:
📊 Threat Analysis
Threat intelligence analysis has linked 104.209.144.33 to malicious activity originating from Boydton, United States, operating on the network of Microsoft Corporation. The address has been under observation since its initial detection. The address has been active for 11 days in our monitoring system, producing 6,883 flagged requests at a rate of ~625.7/day. The IP is classified as hosting/datacenter infrastructure, commonly associated with rented servers used for automated attack campaigns, botnet command-and-control, or vulnerability scanning at scale. The combination of 3 distinct attack vectors indicates a sophisticated, multi-pronged threat actor deploying automated tools that probe multiple attack surfaces simultaneously. With 108 flagged addresses, United States represents a significant presence in our threat database. With a threat score of 280/100, this IP is among the most dangerous addresses in our database. Immediate and complete blocking is strongly recommended.
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.
Related Threats
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.214.122 (350)34.187.158.4 (340)34.186.187.208 (340)104.28.214.116 (340)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.
💡 Content Delivery Network Risks
CDNs can inadvertently mask the true origin of malicious traffic, making attribution difficult. Attackers abuse CDN services to proxy their attacks, leverage cached content for amplification, and exploit misconfigurations in CDN-to-origin connections.