IP Threat Report
165.22.201.231
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 33/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 53/2s | Abnormally fast request rate — automated scanning | +35 | |
| Burst 58/10s | Abnormally fast request rate — automated scanning | +35 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| 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
We have detected 6979 malicious IPs from this autonomous system.
Recommendations
Actions taken & recommended
- IP 165.22.201.231 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 165.22.201.231: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
🌊 Traffic Flood Defense
IP 165.22.201.231 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 165.22.201.231: 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
165.22.201.231 has been assigned a threat score of 140/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
IP address 165.22.201.231 has been traced to Amsterdam, Netherlands, operating on the network of DigitalOcean, LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. The address has been active for 1 days in our monitoring system, producing 57 flagged requests at a rate of ~57/day. Operating from datacenter infrastructure, this IP is typical of addresses used in organized attack operations. Cloud and VPS providers are commonly exploited as launching platforms for automated scanning. With 3 different attack patterns detected, this IP exhibits behavior characteristic of advanced automated scanning frameworks. Our records show 2,853 malicious IPs originating from Netherlands, positioning it as a major contributor to global threat activity. With a threat score of 140/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 Netherlands
91.92.43.144 (358)91.92.43.186 (358)91.92.43.190 (358)91.92.43.157 (358)91.92.43.153 (358)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.
💡 WebSocket Security Considerations
WebSocket connections bypass traditional HTTP security controls, creating opportunities for cross-site WebSocket hijacking, denial of service, and data injection. Proper origin validation, authentication, and message rate limiting are essential for secure WebSocket implementations.