Recent telemetry from the SANS Internet Storm Center confirms a resurgence in internet-wide scanning activity targeting Hikvision security cameras. Specifically, threat actors are aggressively probing the Hikvision Intelligent Security API. As we have tracked for years, these devices are perennial targets due to their ubiquity in critical infrastructure and historical security postures. In 2026, this isn't just background noise; these scans are the precursor to device compromise, botnet recruitment, and persistent surveillance. Defenders must treat these API probes as active indicators of hostile reconnaissance.
Technical Analysis
Affected Products:
- Hikvision IP Cameras, NVRs, and DVRs exposing the Intelligent Security API (ISAPI).
- Specifically, devices exposing web interfaces on ports 80, 443, 8080, or 8000.
The Threat Vector:
The Intelligent Security API (ISAPI) is a proprietary interface used for configuration and management. Recent scans focus on enumerating endpoints such as /ISAPI/Security/users and /ISAPI/System/Network/UPNP.
- Attack Chain: The attacker performs large-scale horizontal scanning -> Identifies exposed Hikvision interfaces -> Probes for authentication bypasses or default credentials (CVEs from 2021-2023 are frequently reused in these automated scripts, even if the specific scanner targets the API structure). -> Establishes persistence.
- Exploitation Status: Confirmed active scanning (Internet-wide). Honeypots are detecting high-frequency attempts to interact with API endpoints, likely seeking unpatched units or weak passwords to facilitate Mirai-like botnet integration or remote access trojan (RAT) installation.
CVE Note: While the specific news item highlights the scan activity rather than a specific new CVE identifier, historical vulnerabilities in the ISAPI interface are frequently the target. Defenders should assume legacy unpatched flaws are being sought.
Detection & Response
The following rules are designed to detect the probing of the Hikvision Intelligent Security API on web servers and proxy logs.
SIGMA Rules
---
title: Hikvision ISAPI Intelligent Security API Probe
id: 89c5d234-1a3b-4c5d-9e6f-1a2b3c4d5e6f
status: experimental
description: Detects reconnaissance attempts probing Hikvision Intelligent Security API endpoints (ISAPI).
references:
- https://isc.sans.edu/diary/33164
author: Security Arsenal
date: 2026/07/20
tags:
- attack.reconnaissance
- attack.t1595
- attack.initial_access
- attack.t1190
logsource:
category: webserver
product: apache
detection:
selection:
c-uri|contains:
- '/ISAPI/Security/'
- '/ISAPI/System/'
- '/ISAPI/Event/notification/'
condition: selection
falsepositives:
- Legitimate administrative access from internal subnets
level: medium
---
title: High Frequency Hikvision API Scanning
id: 77a4b1c2-3d4e-5f6a-7b8c-9d0e1f2a3b4c
status: experimental
description: Detects high-frequency requests to Hikvision API paths indicative of automated scanning tools.
references:
- https://isc.sans.edu/diary/33164
author: Security Arsenal
date: 2026/07/20
tags:
- attack.initial_access
- attack.t1190
logsource:
category: webserver
product: nginx
detection:
selection_uri:
c-uri|contains: '/ISAPI/'
filter_legit:
c-ip|cidr:
- '10.0.0.0/8'
- '192.168.0.0/16'
- '172.16.0.0/12'
timeframe: 1m
condition: selection_uri | count() by c-ip > 10 and not filter_legit
falsepositives:
- Authorized internal configuration backups
level: high
KQL (Microsoft Sentinel / Defender)
// Hunt for Hikvision ISAPI probing in Syslog/CEF or CommonSecurityLog
Syslog
| where SyslogMessage contains "/ISAPI/"
| extend RequestPath = extract(@"GET\s+(\/ISAPI\/[^\s]+)", 1, SyslogMessage)
| summarize count() by RequestPath, SourceIP, bin(TimeGenerated, 5m)
| where count_ > 5
| order by count_ desc
| project TimeGenerated, SourceIP, RequestPath, count_
Velociraptor VQL
-- Hunt for established connections on common Hikvision ports
-- This identifies potential active management or callback connections
SELECT Fd, Family, State, RemoteAddr, RemotePort, Pid
FROM listen_sockets()
WHERE RemotePort IN (80, 443, 554, 8000, 8080)
AND State == 'ESTABLISHED'
AND RemoteAddr NOT IN ['127.0.0.1', '::1', '0.0.0.0']
Remediation Script (PowerShell)
<#
.SYNOPSIS
Scans the local subnet for devices responding with Hikvision web headers to identify exposed assets.
.DESCRIPTION
This script attempts to identify Hikvision devices on the local network by checking HTTP headers.
Use only on networks you are authorized to audit.
#>
$Subnet = "192.168.1" # Update to your local subnet prefix
$Ports = @(80, 443, 8080, 8000)
Write-Host "Scanning for Hikvision devices..."
1..254 | ForEach-Object {
$IP = "$Subnet.$_"
foreach ($Port in $Ports) {
try {
$TcpClient = New-Object System.Net.Sockets.TcpClient
$Connect = $TcpClient.BeginConnect($IP, $Port, $null, $null)
$Wait = $Connect.AsyncWaitHandle.WaitOne(200, $false)
if ($Wait) {
$TcpClient.EndConnect($Connect)
# Quick HTTP Header Check
try {
$Response = Invoke-WebRequest -Uri "http://$IP`:$Port" -Method Head -TimeoutSec 2 -ErrorAction SilentlyContinue
if ($Response.Headers['Server'] -like '*Hikvision*' -or $Response.Headers['Server'] -like '*Webs*') {
Write-Host "[ALERT] Hikvision Device Found: $IP`:$Port - $($Response.Headers['Server'])" -ForegroundColor Red
}
} catch {
# Ignore HTTP errors, port was open
}
}
$TcpClient.Close()
} catch {
# Port closed or filtered
}
}
}
Write-Host "Scan complete."
Remediation
Immediate action is required to secure these endpoints against active scanning:
- Network Segmentation: Immediately move Hikvision devices to an isolated VLAN. They should not have direct internet access, nor should they be reachable from the general corporate LAN.
- Disable ISAPI (If Possible): Review the device interface. If the Intelligent Security API is not required for your specific integration (e.g., VMS software), disable it via the web interface (
Configuration -> Network -> Advanced Settings -> Integration Protocol). - Update Firmware: While no specific 2026 CVE is listed in this alert, applying the latest firmware mitigates the vast majority of historical buffer overflows and authentication bypasses these scans rely on.
- Disable UPnP: Ensure Universal Plug and Play (UPnP) is disabled to prevent the device from opening ports on your firewall automatically.
- Firewall Blocking: Configure edge firewalls to drop inbound traffic on ports 80, 443, 8000, and 8080 originating from the internet to IP ranges known to contain IoT devices.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.