ABUSE.MOM
THREAT REPORT

IP Threat Report
167.160.182.108

ABUSE.MOM — BEHAVE OR GET EXPOSED

Generated: 2026-05-22 09:08:44
First seen: 2026-04-17 22:00:05
Last seen: 2026-04-17 22:00:05
105

⛔ Verdict: BLOCK

This IP address has been classified as a source of malicious automated activity. Threat score: 105/100. Total malicious requests observed: 1.

DANGER_PATHRATIO_404REDIRECT_PROBEREFERER
01

Geolocation & Classification

IP Address
167.160.182.108
Type
Residential
Country
🇺🇸 United States
City
Los Angeles
ISP
HostPapa
Organization
David Wu
Autonomous System
AS36352 HostPapa
Hit Count
1
02

Detection Signatures

SignatureDescriptionPointsSeverity
Danger medium hits: 10Medium-risk: admin panels, config files+60
404 ratio 40-60%Majority of requests returned 404 — enumeration+15
Probe pattern 302->404 same pathBehavioral anomaly detected by automated analysis+20
Foreign referer seenReferer from unrelated external domain+10
Σ = 105
03

Observed Activity

Reconstructed HTTP requests from server access logs. Target domains redacted for security.

[redacted]
GET
/
200
Requests shown: 1 · HTTP 404: 0 · Dangerous patterns: 0

* Typical request patterns for detected signatures. Actual target domains are redacted.

04

Timeline

2026-04-17 22:00:05
First malicious request detected
IP entered monitoring from server access logs
During observation
Multiple detection signatures triggered
Danger medium hits: 10 (+60), 404 ratio 40-60% (+15), Probe pattern 302->404 same path (+20)
2026-04-17 22:00:05
Last malicious request observed
Total score reached: 105/100
Next cycle
IP blocked — all subsequent requests denied (HTTP 403)
Added to blocklist automatically
05

Network Provider

HostPapa
AS36352 · 🇺🇸 United States
06

Recommendations

Actions taken & recommended

  • IP 167.160.182.108 is blocked at application level (HTTP 403)
  • Consider blocking at firewall level (iptables/CSF) to reduce server load
  • Other malicious IPs detected in the same /24 subnet — consider blocking 167.160.182.0/24
  • Report abuse to the network provider via their abuse contact
  • Ensure sensitive files (.env, .git, backups) are not accessible from the web

🔎 Directory Scan Defense

IP 167.160.182.108 is enumerating directories. Configure fail2ban apache-404 jail after 10+ 404 errors. Disable directory listings. Normalize all 404 responses.

07

Neighbors in 167.160.182.0/24

Other blocked IPs from the same /24 subnet — indicates systematic abuse from this network range.

08

Open Ports & Services

Network reconnaissance data from Shodan. Open ports may indicate running services, misconfigurations, or potential attack surfaces.

OPEN PORTS (7)
PortServiceRiskDescription
80HTTPLowHTTP web server — standard web traffic
1344UnknownLowService on port 1344
3128UnknownLowService on port 3128
8000UnknownLowService on port 8000
8080HTTP-AltLowHTTP alternative port — often used for admin panels or proxies
8800UnknownLowService on port 8800
52951UnknownLowService on port 52951
KNOWN VULNERABILITIES (CVE) (59)
CVE IDLink
CVE-2019-18860NVD →
CVE-2025-59362NVD →
CVE-2023-46728NVD →
CVE-2023-46724NVD →
CVE-2024-45802NVD →
CVE-2019-12524NVD →
CVE-2022-41318NVD →
CVE-2020-8517NVD →
CVE-2021-31807NVD →
CVE-2020-25097NVD →
CVE-2020-14058NVD →
CVE-2020-15049NVD →
CVE-2025-62168NVD →
CVE-2019-12520NVD →
CVE-2019-18677NVD →
CVE-2019-18679NVD →
CVE-2021-31808NVD →
CVE-2023-49286NVD →
CVE-2021-28652NVD →
CVE-2020-8449NVD →
CVE-2018-1000024NVD →
CVE-2026-33526NVD →
CVE-2023-49285NVD →
CVE-2018-19131NVD →
CVE-2019-12522NVD →
+34 more

🔴 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.

DETECTED TECHNOLOGIES
squid-cache:squid:3.5.20

Data source: Shodan InternetDB. Scanned independently of abuse.mom.

09

Blacklist Status (DNSBL)

This IP was checked against major DNS-based blacklists used by mail servers and firewalls worldwide.

✓ Clean
dnsbl.sorbs.net
✓ Clean
ix.dnsbl.manitu.net
✓ Clean
zen.spamhaus.org
✓ Clean
bl.spamcop.net
✓ Clean
dnsbl-1.uceprotect.net
✓ Clean
b.barracudacentral.org
✓ Clean
truncate.gbudb.net
✓ Clean
psbl.surriel.com

Checked: Spamhaus, SpamCop, Barracuda, SORBS, CBL, UCEProtect. Results may change over time.

10

Threat Analysis

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:

Path Enumeration

📊 Threat Analysis

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.

11

Related Threats

🇺🇸 Top threats from United States

104.28.246.115 (350)104.28.246.113 (340)104.28.246.116 (340)104.28.235.58 (340)104.28.246.122 (340)View all →

🏢 Same network: AS36352

23.94.40.119 (318)172.245.95.40 (280)23.94.28.183 (255)192.227.215.35 (255)172.245.214.62 (245)View all →
12

Security Intelligence

💡 File Upload Vulnerabilities

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.

💡 Subnet-Level vs IP-Level Blocking

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.

🔍 Check Any IP Address

Share this report: