IP Threat Report
104.199.36.53
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 | |
| Burst 112/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 112/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 114/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 114/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 115/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 115/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 116/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 116/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 117/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 117/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 118/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 119/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 120/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 120/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 125/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 127/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 128/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 129/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 129/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 130/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 130/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 132/10s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 132/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 10 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 15 | Medium-risk: admin panels, config files | +60 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Danger strong hits: 144 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 146 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 220 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 71 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 72 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 73 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 74 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 75 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 76 | High-risk paths: shells, RCE vectors, exploits | +100 | |
| Danger strong hits: 79 | 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.199.36.53 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
🔎 Directory Scan Defense
IP 104.199.36.53 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 104.199.36.53 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.199.36.53: 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.199.36.53 has been assigned a threat score of 278/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
IP address 104.199.36.53 has been traced to Brussels, Belgium, operating on the network of Google LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 23 days, this IP generated 1,604 malicious requests, averaging approximately 69.7 requests per 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. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Belgium currently accounts for 842 blocked IPs in our database, making it a major source of malicious traffic. A score of 278/100 places this address in the top tier of severity. Block and investigate any historical connections.
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
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.
💡 GeoIP Blocking Considerations
Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.