IP Threat Report
2.25.132.96
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Malicious Activity | Behavioral anomaly detected by automated analysis | +0 |
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
Recommendations
Actions taken & recommended
- IP 2.25.132.96 is blocked at application level (HTTP 403)
- Consider blocking at firewall level (iptables/CSF) to reduce server load
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
⚙️ Defensive Recommendations
Block 2.25.132.96 at the network perimeter. Implement defense-in-depth combining IP blocking with application-layer protections.
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
2.25.132.96 has been assigned a threat score of 75/100 (High). At this threat level, the IP is considered high risk. Firewall rules should be updated to deny traffic from this source.
📊 Threat Analysis
The address 2.25.132.96 originates from City of London, United Kingdom, operating on the network of EE Limited. It was identified through automated analysis of incoming network traffic across monitored endpoints. The address has been active for 7 days in our monitoring system, producing 170 flagged requests at a rate of ~24.3/day. United Kingdom currently accounts for 101 blocked IPs in our database, making it a significant source of malicious traffic. The score of 75/100 indicates a confirmed malicious actor. Network-level blocking is appropriate.
Related Threats
🇬🇧 Top threats from United Kingdom
104.28.208.60 (340)104.28.240.60 (340)91.230.225.239 (305)91.230.225.36 (305)91.230.225.147 (305)View all →Security Intelligence
💡 Subnet-Level vs IP-Level Blocking
When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.
💡 Backup and Recovery Against Ransomware
Immutable, offline backups remain the most effective defense against ransomware. The 3-2-1 rule — three copies on two media types with one offsite — combined with regular recovery testing ensures business continuity after encryption attacks.