
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 |
Reconstructed HTTP requests from server access logs. Target domains redacted for security.
* Typical request patterns for detected signatures. Actual target domains are redacted.
IP 167.160.182.108 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 |
| 1344 | Unknown | Low | Service on port 1344 |
| 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 |
| 52951 | Unknown | Low | Service on port 52951 |
| CVE ID | Link |
|---|---|
| CVE-2019-18860 | NVD → |
| CVE-2025-59362 | NVD → |
| CVE-2023-46728 | NVD → |
| CVE-2023-46724 | NVD → |
| CVE-2024-45802 | NVD → |
| CVE-2019-12524 | NVD → |
| CVE-2022-41318 | NVD → |
| CVE-2020-8517 | NVD → |
| CVE-2021-31807 | NVD → |
| CVE-2020-25097 | NVD → |
| CVE-2020-14058 | NVD → |
| CVE-2020-15049 | NVD → |
| CVE-2025-62168 | NVD → |
| CVE-2019-12520 | NVD → |
| CVE-2019-18677 | NVD → |
| CVE-2019-18679 | NVD → |
| CVE-2021-31808 | NVD → |
| CVE-2023-49286 | NVD → |
| CVE-2021-28652 | NVD → |
| CVE-2020-8449 | NVD → |
| CVE-2018-1000024 | NVD → |
| CVE-2026-33526 | NVD → |
| CVE-2023-49285 | NVD → |
| CVE-2018-19131 | NVD → |
| CVE-2019-12522 | 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.
167.160.182.108 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 167.160.182.108 originates from Los Angeles, United States, operating on the network of HostPapa. It was identified through automated analysis of incoming network traffic across monitored endpoints. During its 1-day observation window, we recorded 1 hostile requests from this IP — roughly 1 per day on average. The address is classified as residential, meaning it likely belongs to an end-user ISP connection. Malicious activity from residential IPs typically indicates device compromise or botnet membership. Active path scanning has been detected — this IP probes for hundreds of common file and directory names. With 203 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.
When multiple IPs in a subnet show malicious behavior, subnet blocking efficiently neutralizes the threat. However, overly broad blocking risks impacting legitimate users. Analysis of subnet ownership and historical behavior guides appropriate blocking scope.