
ABUSE.MOM — BEHAVE OR GET EXPOSED
| 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 |
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 199.34.89.238: 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 |
|---|---|---|---|
| 4444 | Unknown | Low | Service on port 4444 |
| 8000 | Unknown | Low | Service on port 8000 |
| CVE ID | Link |
|---|---|
| CVE-2026-33515 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2026-32748 | NVD → |
🔴 This host has 30 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.
199.34.89.238 has been assigned a threat score of 105/100 (Critical). With this rating, the IP falls into the critical severity bracket — among the most dangerous addresses in our monitoring database.
The following attack categories were identified:
Network traffic from 199.34.89.238, located in Los Angeles, United States, operating on the network of Sprious LLC, has been classified as malicious by our automated threat scoring engine. Our sensors captured 2 malicious requests from this address across a 42-day span, reflecting a sustained attack cadence of ~0 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 203 flagged addresses, United States represents a significant presence in our threat database. 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.
Command injection occurs when attackers insert operating system commands through application inputs. Successful exploitation grants direct server access, enabling data theft, malware installation, and lateral movement across networks.
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.