
ABUSE.MOM — BEHAVE OR GET EXPOSED
| Signature | Description | Points | Severity |
|---|---|---|---|
| Danger medium hits: 10 | 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: 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.
Block scanning from 192.126.163.37: 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 |
|---|---|---|---|
| 3128 | Unknown | Low | Service on port 3128 |
| 8000 | Unknown | Low | Service on port 8000 |
| 8080 | HTTP-Alt | Low | HTTP alternative port — often used for admin panels or proxies |
| 8800 | Unknown | Low | Service on port 8800 |
| 21242 | Unknown | Low | Service on port 21242 |
| 52931 | Unknown | Low | Service on port 52931 |
| CVE ID | Link |
|---|---|
| CVE-2021-33620 | NVD → |
| CVE-2019-18676 | NVD → |
| CVE-2019-12526 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2021-28116 | NVD → |
| CVE-2018-19132 | NVD → |
| CVE-2018-1000027 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2020-15810 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2020-8450 | NVD → |
| CVE-2020-15811 | NVD → |
| CVE-2024-37894 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2018-19131 | NVD → |
🔴 Security scanning identified 56 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.
192.126.163.37 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:
Threat intelligence analysis has linked 192.126.163.37 to malicious activity originating from Seattle, United States, operating on the network of EliteWork LLC. The address has been under observation since its initial detection. Our sensors captured 3 malicious requests from this address across a 14-day span, reflecting a sustained attack cadence of ~0.2 requests per day. 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. 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.
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.
SSTI occurs when user input is embedded in server-side templates without sanitization. Successful exploitation often leads to remote code execution, as template engines typically have access to powerful server-side functionality.