Actively exploited Security news
Attackers abuse GeoVision camera software to disable Defender and mine crypto at 13 organizations
On 13 November 2026, Huntress described a series of intrusions in which attackers got into Windows machines through internet-exposed GeoVision camera management software. At 13 organizations they used a vulnerable driver to knock out Microsoft Defender and installed a Monero miner. Here are the indicators and how to check your hosts.
Key points
- Per Huntress, every intrusion started from GeoStartupAgentService.exe, often running as SYSTEM, on hosts with GeoVision exposed to the internet. Huntress does not say which vulnerability was exploited.
- The attackers loaded a vulnerable driver (BYOVD) and used IFEO registry keys to stop Defender and Windows Security from launching.
- A custom Go loader pulls the XMRig miner, runs every 15 minutes via a scheduled task and finds new servers through BitTorrent DHT - botnet-like infrastructure, Huntress says.
What happened
The Huntress SOC published an advisory on 13 November 2026: attackers breached Windows machines at 13 organizations across several industries through camera and access-control management software from Taiwanese vendor GeoVision. Most of the activity took place on 8-10 November 2026. Shodan tied the affected IP addresses to GeoVision devices or management interfaces exposed to the internet. Huntress does not say which vulnerability was used.
How the attack worked
GeoStartupAgentService.exespawnedcmd.exeand a PowerShell download cradle that pulled a script from attacker infrastructure.- The scripts looked for writable folders, checked whether Microsoft Defender was running and downloaded
kvckiller.sys(wsftprm.syson VirusTotal), a known vulnerable driver abused to tamper with antivirus. - Image File Execution Options registry keys redirected
MsMpEng.exe,SecurityHealthService.exeandSecurityHealthSystray.exetosystray.exe, so the protection never starts. - The Go loader
update.exedownloaded XMRig asApplyUpdate.exe. It embeds a BitTorrent DHT client and a PKARR resolver, letting the operator move servers without losing access.
How to tell if you were hit
Indicators from the Huntress advisory (defanged - replace [.] with a dot before using them in detections):
SHA256 of scripts a, b, c: b673c4d707828abedc767a2be6badef7454492e62c37e30cf3cc5a402fd3647b
SHA256 wsftprm.sys / kvckiller.sys: ff5dbdcf6d7ae5d97b6f3ef412df0b977ba4a844c45b30ca78c0eeb2653d69a8
SHA256 update.exe (loader): f1235751c9e48e5732b7b183dc2bb175a19e4c6401dfd0e96b4cfdd0d8c54b4c
2.59.133[.]151 likely exploitation source (contacted by WebCamServer.exe)
45.32.117[.]34 hosted scripts a, b, c
156.246.94[.]183 loader server
cctv-update[.]top loader domain (registered 7 Nov 2026)
Scheduled tasks: PackageUpdater, PackageUpdater_Startup
Path: C:\WINDOWS\system32\config\systemprofile\update.exe
Also hunt for cmd.exe or powershell.exe whose parent is GeoStartupAgentService.exe, DNS queries to 8.8.8.8, 8.8.4.4 or 1.1.1.1 from anything other than the system DNS client, outbound UDP on port 6881 from WebCamServer.exe, and schtasks /Create launched by update.exe. Our IOC extractor pulls indicators out of longer reports.
What to do
- Remove internet access to GeoVision - keep management behind a VPN or an IP allowlist.
- Update GeoVision software to the latest vendor release.
- Sweep hosts for the indicators above. If you find a hit, isolate the machine and preserve evidence before deleting files.
- Check IFEO keys (
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options) for Defender processes. - Treat camera and access-control software as part of your corporate network, with patching, monitoring and EDR.
Timeline
- 7 Nov 2026 -
cctv-update[.]topregistered. - 8-10 Nov 2026 - most intrusions.
- 13 Nov 2026 - Huntress advisory.
Details come from the Huntress advisory of 13 Nov 2026 (verified 16 Nov 2026). Huntress gives inconsistent figures for the number of affected accounts, so we leave that out.
FAQ
Is this just mining, or data theft too?
Huntress only saw cryptomining and found no evidence that access was sold. But the attacker had SYSTEM rights and the loader can fetch anything else, so treat an affected host as fully compromised.
Which GeoVision flaw was exploited?
Huntress doesn't name it. Either way, camera management should not be reachable from the internet and should run the latest vendor release.
How do I know whether our GeoVision is reachable from the internet?
Review firewall rules and port forwards to machines running GeoVision software, and try opening the management interface from an address outside your network. Huntress tied the affected hosts to GeoVision interfaces that Shodan saw as publicly exposed.
Sources
Spotted a mistake? Let us know and we will correct it openly.