
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 3 | Medium-risk: admin panels, config files | +30 | |
| 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: 7 | 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 167.160.75.212: 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-2021-31806 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2026-32748 | NVD → |
| CVE-2021-33620 | NVD → |
🔴 Security scanning identified 30 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.
167.160.75.212 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:
Our monitoring infrastructure has identified 167.160.75.212, geolocated to New York, United States, operating on the network of Emeigh Investments LLC, as a source of suspicious network activity. The address has been active for 16 days in our monitoring system, producing 4 flagged requests at a rate of ~0.3/day. This is a residential IP address, suggesting a compromised home device such as a router, smart appliance, or infected workstation participating in a botnet. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. United States currently accounts for 204 blocked IPs in our database, making it a significant source of malicious traffic. 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.
WordPress sites face constant automated attacks targeting xmlrpc.php for brute force amplification, wp-login.php for credential theft, and vulnerable plugins for remote code execution. Over 90% of CMS-based attacks specifically target WordPress installations.
Zero trust eliminates implicit trust based on network location. Every access request is verified regardless of source, minimizing the impact of compromised credentials or network breaches. Implementation requires strong identity verification and continuous authorization.