
ABUSE.MOM — BEHAVE OR GET EXPOSED
| 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 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
Block scanning from 23.94.230.62: rate-limit 404 responses per IP, deploy a honeypot 404 page, ensure no backup files are web-accessible.
Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.
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 |
| 21242 | Unknown | Low | Service on port 21242 |
| 52931 | Unknown | Low | Service on port 52931 |
| 52951 | Unknown | Low | Service on port 52951 |
| CVE ID | Link |
|---|---|
| CVE-2025-62168 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2020-11945 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2019-12526 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2019-12523 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2019-12522 | 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.
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.
23.94.230.62 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 23.94.230.62, geolocated to Los Angeles, United States, operating on the network of HostPapa, as a source of suspicious network activity. Our sensors captured 5 malicious requests from this address across a 16-day span, reflecting a sustained attack cadence of ~0.3 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 204 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.
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.
CAPTCHAs remain a primary bot defense but face increasing bypass rates from AI-powered solvers. Modern alternatives include invisible behavioral analysis, proof-of-work challenges, and device fingerprinting that detect bots without impacting user experience.