
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 4 | Medium-risk: admin panels, config files | +40 | |
| 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 172.96.84.170 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
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 |
| CVE ID | Link |
|---|---|
| CVE-2021-28116 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2023-46728 | NVD → |
🔴 This host has 28 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.
172.96.84.170 has been assigned a threat score of 70/100 (High). This score indicates high threat severity. The IP has shown clear patterns of malicious behavior that warrant immediate defensive measures.
The following attack categories were identified:
Network traffic from 172.96.84.170, located in Chicago, United States, operating on the network of Emeigh Investments LLC, has been classified as malicious by our automated threat scoring engine. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 201 flagged addresses, United States represents a significant presence in our threat database. A threat score of 70/100 places this IP in the high-risk category. Blocking at the firewall level is recommended.
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.
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.
Cross-Origin Resource Sharing misconfigurations can expose sensitive APIs to unauthorized origins. Wildcard policies, reflected origins, and null origin allowlisting create vulnerabilities that attackers exploit for data theft and unauthorized actions.