IP Threat Report
66.63.171.162
ABUSE.MOM — BEHAVE OR GET EXPOSED
Geolocation & Classification
Detection Signatures
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 | |
| Foreign referer seen | Referer from unrelated external domain | +10 |
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 66.63.171.162 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 66.63.171.0/24
- Report abuse to the network provider via their abuse contact
- Ensure sensitive files (.env, .git, backups) are not accessible from the web
🔎 Directory Scan Defense
IP 66.63.171.162 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
Neighbors in 66.63.171.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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 3128 | Unknown | Low | Service on port 3128 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| CVE ID | Link |
|---|---|
| CVE-2019-12529 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2019-12525 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2018-1000027 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2018-19132 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2019-18678 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2025-59362 | NVD → |
🔴 Security scanning identified 59 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
66.63.171.162 has been assigned a threat score of 105/100 (Critical). This is a critical-level threat. Systems administrators should treat this IP as hostile and block all inbound connections without exception.
The following attack categories were identified:
📊 Threat Analysis
IP address 66.63.171.162 has been traced to Los Angeles, United States, operating on the network of HostPapa. Our threat detection systems have flagged this address based on observed malicious behavior patterns. Over a period of 9 days, this IP generated 2 malicious requests, averaging approximately 0.2 requests per day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 202 blocked IPs in our database, making it a significant source of malicious traffic. 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.
💡 IP Geolocation Accuracy Limitations
IP geolocation databases provide approximate locations with varying accuracy. City-level geolocation is typically 50-80% accurate, while country-level exceeds 95%. VPNs, proxies, and mobile networks further reduce reliability, making geolocation a useful but imperfect intelligence signal.