
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 6 | 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 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 192.126.214.37 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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 8000 | Unknown | Low | Service on port 8000 |
| 8800 | Unknown | Low | Service on port 8800 |
| 21242 | Unknown | Low | Service on port 21242 |
| 52951 | Unknown | Low | Service on port 52951 |
| CVE ID | Link |
|---|---|
| CVE-2021-28116 | NVD → |
| CVE-2023-46847 | NVD → |
| CVE-2019-12522 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2019-18678 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2023-49288 | NVD → |
| CVE-2019-12529 | NVD → |
| CVE-2016-10003 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2021-28651 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2025-62168 | NVD → |
🔴 This host has 56 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.
192.126.214.37 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 192.126.214.37 originates from Seattle, United States, operating on the network of EliteWork LLC. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 30-day observation window, we recorded 6 hostile requests from this IP — roughly 0.2 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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. Our records show 138 malicious IPs originating from United States, positioning it as a significant contributor to global threat activity. 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.
XSS attacks inject malicious scripts into web pages viewed by other users. Reflected XSS uses crafted URLs, while stored XSS persists in databases. Both types can steal session cookies, redirect users, or deface websites.
Modern attacks increasingly target APIs rather than traditional web interfaces. Attackers enumerate endpoints, test for broken authentication, and exploit excessive data exposure. API attacks are harder to detect as they mimic legitimate programmatic access patterns.