IP Threat Report
64.23.135.164
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| UA suspicious (short/empty) | Behavioral anomaly detected by automated analysis | +15 | |
| Danger strong hits: 3 | High-risk paths: shells, RCE vectors, exploits | +75 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +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 64.23.135.164 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
🤖 User-Agent Anomaly Defense
IP 64.23.135.164 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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 |
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 443 | HTTPS | Low | HTTPS web server — encrypted web traffic |
| 3306 | MySQL | High | MySQL database — should never be exposed to the internet |
| 8055 | Unknown | Low | Service on port 8055 |
⚠️ 1 high-risk port detected on 64.23.135.164. These services should not be publicly accessible without strict firewall rules.
| CVE ID | Link |
|---|---|
| CVE-2025-50080 | NVD → |
| CVE-2025-50097 | NVD → |
| CVE-2025-50084 | NVD → |
| CVE-2025-50101 | NVD → |
| CVE-2025-50102 | NVD → |
| CVE-2025-50087 | NVD → |
| CVE-2025-50078 | NVD → |
| CVE-2025-50086 | NVD → |
| CVE-2025-50099 | NVD → |
| CVE-2025-50077 | NVD → |
| CVE-2025-50091 | NVD → |
| CVE-2025-50098 | NVD → |
| CVE-2025-50081 | NVD → |
| CVE-2025-50082 | NVD → |
| CVE-2025-50076 | NVD → |
| CVE-2025-50083 | NVD → |
| CVE-2025-50096 | NVD → |
| CVE-2025-50093 | NVD → |
| CVE-2026-21964 | NVD → |
| CVE-2025-50100 | NVD → |
| CVE-2025-50092 | NVD → |
| CVE-2025-50088 | NVD → |
| CVE-2025-50079 | NVD → |
| CVE-2025-50085 | NVD → |
| CVE-2025-50104 | NVD → |
🔴 This host has 25 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
64.23.135.164 has been assigned a threat score of 110/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
📊 Threat Analysis
The address 64.23.135.164 originates from Santa Clara, United States, operating on the network of DigitalOcean, LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Over a period of 1 days, this IP generated 1 malicious requests, averaging approximately 1 requests per day. Classified as a hosting IP, this address likely runs on a rented server or cloud instance. Attackers prefer datacenter IPs for their high bandwidth and disposable nature. Detected suspicious User-Agent anomalies including empty, forged, or rapidly rotating UA strings — characteristic of automated scanning tools. United States currently accounts for 128 blocked IPs in our database, making it a significant source of malicious traffic. A score of 110/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
🇺🇸 Top threats from United States
104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →Security Intelligence
💡 User-Agent Analysis Techniques
Analyzing User-Agent strings reveals automated tools masquerading as legitimate browsers. Inconsistencies between claimed browser capabilities and actual behavior, impossible version combinations, and known scanner signatures help identify malicious clients.
💡 Zero Trust Architecture Principles
Zero trust eliminates implicit trust based on network location. Every access request is verified regardless of source, minimizing the impact of compromised credentials or network breaches. Implementation requires strong identity verification and continuous authorization.