
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| Danger medium hits: 6 | Medium-risk: admin panels, config files | +60 | |
| Foreign referer | Referer from unrelated external domain | +10 | |
| Foreign referer seen | Referer from unrelated external domain | +10 | |
| Probe 302→404 | Behavioral anomaly detected by automated analysis | +20 | |
| Probe pattern 302->404 same path | Behavioral anomaly detected by automated analysis | +20 |
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 209.163.116.0: 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-2021-28116 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2024-25111 | 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.
209.163.116.0 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:
The address 209.163.116.0 originates from New York, United States, operating on the network of Emeigh Investments LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. Our sensors captured 588 malicious requests from this address across a 11-day span, reflecting a sustained attack cadence of ~53.5 requests per day. 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. Our records show 204 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. 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.
Credential stuffing uses stolen username-password pairs from data breaches to attempt logins across many websites. Since users frequently reuse passwords, these automated attacks achieve success rates of 0.1-2%, which translates to thousands of compromised accounts from millions of attempts.
Prototype pollution manipulates JavaScript object prototypes to inject properties that affect all objects in an application. This can lead to denial of service, property injection, and in some cases remote code execution in Node.js applications.