IP Threat Report
159.65.136.132
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger strong hits: 2 | High-risk paths: shells, RCE vectors, exploits | +50 | |
| Danger medium hits: 1 | Medium-risk: admin panels, config files | +10 | |
| 404 ratio >= 60% | Majority of requests returned 404 — enumeration | +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 159.65.136.132 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 159.65.136.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🤖 User-Agent Anomaly Defense
IP 159.65.136.132 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
🔎 Directory Scan Defense
IP 159.65.136.132 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Neighbors in 159.65.136.0/24
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
Open Ports & Services
Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.
| Port | Service | Risk | Description |
|---|---|---|---|
| 22 | SSH | Low | Secure Shell — common brute force target for remote access |
| 111 | Unknown | Low | Service on port 111 |
| CVE ID | Link |
|---|---|
| CVE-2019-6111 | NVD → |
| CVE-2021-41617 | NVD → |
| CVE-2023-38408 | NVD → |
| CVE-2023-51385 | NVD → |
| CVE-2019-6110 | NVD → |
| CVE-2016-20012 | NVD → |
| CVE-2020-15778 | NVD → |
| CVE-2019-6109 | NVD → |
| CVE-2021-36368 | NVD → |
| CVE-2023-48795 | NVD → |
| CVE-2023-51767 | NVD → |
| CVE-2018-15919 | NVD → |
| CVE-2008-3844 | NVD → |
| CVE-2025-32728 | NVD → |
| CVE-2020-14145 | NVD → |
| CVE-2007-2768 | NVD → |
| CVE-2018-20685 | NVD → |
| CVE-2018-15473 | NVD → |
| CVE-2017-15906 | NVD → |
| CVE-2025-26465 | NVD → |
🔴 This host has 20 known CVEs associated with its exposed services. This volume strongly suggests severely outdated software. Review each CVE in the NVD database.
Data source: Shodan InternetDB. Scanned independently of abuse.mom.
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
159.65.136.132 has been assigned a threat score of 110/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
159.65.136.132 is registered in Singapore, Singapore, operating on the network of DigitalOcean, LLC. This IP first appeared in our threat feeds after triggering multiple behavioral detection signatures. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This address belongs to a datacenter or cloud hosting provider. Hosting IPs are frequently leveraged by threat actors who rent cheap VPS instances specifically for conducting attacks. The dual attack vectors of User-Agent Anomaly combined with Path Enumeration indicate a coordinated assault rather than opportunistic scanning. With 141 flagged addresses, Singapore represents a significant presence in our threat database. With a threat score of 110/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
Security Intelligence
💡 HTTP Header Analysis for Threat Detection
Examining HTTP headers beyond User-Agent reveals attack tools and automated scripts. Missing standard headers, unusual ordering, non-standard values, and inconsistencies with claimed client identity all serve as reliable detection signals.
💡 API Abuse and Enumeration
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.