
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 2 | Medium-risk: admin panels, config files | +20 | |
| 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 | |
| 404 ratio 40-60% | Majority of requests returned 404 — enumeration | +15 | |
| UA changed for same IP | Multiple User-Agents — bot rotation technique | +25 | |
| Danger medium hits: 5 | Medium-risk: admin panels, config files | +50 | |
| Danger medium hits: 6 | 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.
IP 138.229.110.197 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.
IP 138.229.110.197 shows suspicious UA behavior. Block empty User-Agent requests. Implement JavaScript-based bot detection for sensitive endpoints.
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 |
|---|---|---|---|
| 8000 | Unknown | Low | Service on port 8000 |
| CVE ID | Link |
|---|---|
| CVE-2023-49288 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2024-25111 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2024-25617 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2021-28662 | NVD → |
| CVE-2022-41317 | NVD → |
| CVE-2023-50269 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2023-46846 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-5824 | NVD → |
🔴 Security scanning identified 27 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.
138.229.110.197 has been assigned a threat score of 120/100 (Critical). This places it in the critical threat category. Immediate blocking is strongly advised across all network perimeters.
The following attack categories were identified:
Our monitoring infrastructure has identified 138.229.110.197, geolocated to San Francisco, United States, operating on the network of Emeigh Investments LLC, as a source of suspicious network activity. During its 69-day observation window, we recorded 6 hostile requests from this IP — roughly 0.1 per day on average. 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. Two attack patterns were identified (Path Enumeration and User-Agent Anomaly), suggesting a semi-automated campaign that targets multiple vulnerabilities. Our records show 206 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. A score of 120/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.
IPs originating from data centers and hosting providers account for a disproportionate amount of malicious traffic. Compromised VPS instances, bulletproof hosting, and abused trial accounts create persistent attack infrastructure that can be difficult to shut down.
Request smuggling exploits differences in how front-end and back-end servers parse HTTP requests. This technique can bypass security controls, poison web caches, and hijack other users sessions by desynchronizing request boundaries.