IP Threat Report
167.160.66.210
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 |
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 167.160.66.210 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 167.160.66.0/24
- 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 167.160.66.210: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Neighbors in 167.160.66.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 |
|---|---|---|---|
| 4444 | Unknown | Low | Service on port 4444 |
| 8000 | Unknown | Low | Service on port 8000 |
| CVE ID | Link |
|---|---|
| CVE-2025-59362 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-5824 | NVD → |
🔴 Security scanning identified 27 vulnerability entries on this host. This volume strongly suggests severely outdated software. Consult NVD advisories for details.
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
167.160.66.210 has been assigned a threat score of 105/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
IP address 167.160.66.210 has been traced to San Francisco, United States, operating on the network of Sprious LLC. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Our sensors captured 2 malicious requests from this address across a 10-day span, reflecting a sustained attack cadence of ~0.2 requests per day. This residential IP is likely a compromised consumer device. Home routers and IoT equipment with default credentials are prime targets for botnet operators. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 202 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. At 105/100, this is an extremely high-risk address. All traffic should be considered hostile.
This IP is classified as residential, suggesting it may belong to a compromised home device, IoT botnet member, or an infected personal computer. Residential IPs involved in attacks often indicate malware infection without the owner's knowledge.
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
💡 File Upload Vulnerabilities
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.
💡 Residential Proxy Networks
Residential proxies route traffic through real home internet connections, making malicious traffic appear to come from legitimate users. Some networks install proxy software bundled with free applications, unknowingly conscripting millions of devices.