
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 7 | 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: 3 | Medium-risk: admin panels, config files | +30 | |
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +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 138.229.107.190: 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-2025-54574 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2023-49288 | NVD → |
🔴 This host has 27 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.
138.229.107.190 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:
The address 138.229.107.190 originates from Secaucus, 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 13 malicious requests from this address across a 43-day span, reflecting a sustained attack cadence of ~0.3 requests per 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. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. United States currently accounts for 201 blocked IPs in our database, making it a significant source of malicious traffic. 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.
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.
SSH servers face constant brute force attacks targeting common usernames and weak passwords. Key-based authentication, fail2ban, non-standard ports, and IP allowlisting dramatically reduce the attack surface. Monitoring auth logs reveals active campaigns and compromised credentials.