
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 | |
| Danger medium hits: 10 | 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.178: 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 |
|---|---|---|---|
| 80 | HTTP | Low | HTTP web server — standard web traffic |
| 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 |
| CVE ID | Link |
|---|---|
| CVE-2024-37894 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2019-12519 | NVD → |
| CVE-2021-31806 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2021-33620 | NVD → |
| CVE-2016-10002 | NVD → |
| CVE-2020-24606 | NVD → |
| CVE-2021-46784 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2019-12522 | NVD → |
| CVE-2019-13345 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2025-54574 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2026-33515 | NVD → |
| CVE-2019-12521 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2020-14058 | NVD → |
🔴 This host has 59 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.163.178 has been assigned a threat score of 105/100 (Critical). This represents a critical risk level. Our detection systems have flagged multiple high-confidence indicators of malicious intent from this address.
The following attack categories were identified:
The address 192.126.163.178 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. The address has been active for 6 days in our monitoring system, producing 3 flagged requests at a rate of ~0.5/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. The IP exhibits directory enumeration behavior, systematically requesting non-existent paths to discover hidden files and misconfigured resources. With 138 flagged addresses, United States represents a significant presence in our threat database. 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.
Insecure file upload functionality allows attackers to upload web shells, malware, or scripts that execute on the server. Proper validation must check file content, not just extensions, and uploaded files should be stored outside the web root.
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.