
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 | |
| Danger medium hits: 8 | Medium-risk: admin panels, config files | +60 |
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.4: 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 |
| 1344 | Unknown | Low | Service on port 1344 |
| 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 |
| CVE ID | Link |
|---|---|
| CVE-2016-10003 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-12525 | NVD → |
| CVE-2019-12519 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2018-19132 | NVD → |
| CVE-2019-12528 | NVD → |
| CVE-2019-18860 | NVD → |
| CVE-2024-37894 | NVD → |
🔴 This host has 59 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.
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.4 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:
Network traffic from 23.94.230.4, located in Los Angeles, United States, operating on the network of HostPapa, has been classified as malicious by our automated threat scoring engine. Our sensors captured 4 malicious requests from this address across a 10-day span, reflecting a sustained attack cadence of ~0.4 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. With 204 flagged addresses, United States represents a significant presence in our threat database. 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.
Brute force attacks systematically try username and password combinations to gain unauthorized access. Modern attacks leverage credential databases from previous breaches, testing millions of combinations using distributed botnets across multiple IP addresses.
Blocking traffic from specific countries reduces attack surface but impacts legitimate international users. Effective geo-based policies use tiered approaches — blocking, rate limiting, or requiring additional verification based on risk assessment.