
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.
IP 138.229.110.182 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 |
| 8000 | Unknown | Low | Service on port 8000 |
| CVE ID | Link |
|---|---|
| CVE-2024-37894 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2023-5824 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2022-41317 | 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.110.182 has been assigned a threat score of 105/100 (Critical). A score this high marks a critical threat actor. This address has demonstrated persistent, aggressive malicious behavior across multiple detection vectors.
The following attack categories were identified:
The address 138.229.110.182 originates from San Francisco, United States, operating on the network of Emeigh Investments LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 49-day observation window, we recorded 899 hostile requests from this IP — roughly 18.3 per day on average. 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 202 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.
RCE vulnerabilities allow attackers to execute arbitrary code on target servers. These critical flaws often arise from deserialization bugs, template injection, or file upload vulnerabilities, and represent the highest severity class of web application weaknesses.
Effective rate limiting must balance protection against abuse with allowing legitimate traffic bursts. Sliding window algorithms, token buckets, and adaptive thresholds based on client reputation provide layered defense against flooding attacks.