IP Threat Report
196.240.104.59
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 6/2s | Abnormally fast request rate — automated scanning | +35 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 |
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 196.240.104.59 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 196.240.104.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 196.240.104.59 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
🌊 Traffic Flood Defense
IP 196.240.104.59 is generating excessive traffic. Limit connections per source IP. Enable geographic blocking if traffic from this region is unexpected.
Neighbors in 196.240.104.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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
196.240.104.59 has been assigned a threat score of 130/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
📊 Threat Analysis
Network traffic from 196.240.104.59, located in City of London, United Kingdom, operating on the network of Orion Network Limited, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 108 hostile requests from this IP — roughly 108 per day on average. This IP is identified as a VPN or proxy endpoint, commonly used to mask the true origin of attack traffic and bypass geographic or reputation-based blocking. Two attack patterns were identified (Path Enumeration and Request Flooding), suggesting a semi-automated campaign that targets multiple vulnerabilities. With 106 flagged addresses, United Kingdom represents a significant presence in our threat database. At 130/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.
Related Threats
🇬🇧 Top threats from United Kingdom
104.28.240.60 (340)104.28.208.60 (340)91.230.225.239 (305)91.230.225.147 (305)185.92.25.78 (305)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.
💡 IPv6 Scanning Challenges
The vast IPv6 address space makes traditional sequential scanning impractical. However, attackers use DNS records, certificate transparency logs, and predictable address patterns to identify active IPv6 hosts, adapting their techniques to the expanded address space.