
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 10 | 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 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 66.63.178.84 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| 52931 | Unknown | Low | Service on port 52931 |
| 52951 | Unknown | Low | Service on port 52951 |
| CVE ID | Link |
|---|---|
| CVE-2025-54574 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2016-10002 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2018-19132 | NVD → |
🔴 Security scanning identified 56 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.
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.
66.63.178.84 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:
Our monitoring infrastructure has identified 66.63.178.84, geolocated to Los Angeles, United States, operating on the network of HostPapa, as a source of suspicious network activity. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. Operating from a residential network, this IP may represent a compromised home gateway or IoT device that has been drafted into a larger attack infrastructure. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. United States currently accounts for 199 blocked IPs in our database, making it a significant source of malicious traffic. A score of 105/100 places this address in the top tier of severity. Block and investigate any historical connections.
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.
Path traversal attacks attempt to access files outside the intended directory by manipulating file path references. Attackers use sequences like ../ to reach sensitive system files such as /etc/passwd or application configuration files.
Automated response systems can block threats in milliseconds, far faster than human analysts. However, automation requires careful safeguards — rate limits on blocking actions, automatic expiration, and human review queues prevent automated systems from causing self-inflicted outages.