Attackers Used GeoVision Camera Software to Plant a Persistent Miner
Huntress traced exposed camera-management hosts to SYSTEM-level service execution, Defender launch hijacks and scheduled tasks that kept a cryptominer running.

A GeoVision camera-management service launched attacker scripts on hosts at 13 organizations, and some of those hosts ended up running an XMRig cryptominer. Huntress’s November 13 investigation ties the activity to GeoStartupAgentService.exe; on many endpoints the process ran as NT AUTHORITY\SYSTEM. The bulk of the activity Huntress observed happened November 8–10. Camera-management servers need the same endpoint and internet-exposure scrutiny as other Windows servers.
Huntress found exposed GeoVision devices or management interfaces associated with the affected endpoints’ external IP addresses in Shodan. The precise entry flaw and fixed build remain unspecified. Restrict public management access now, and use process ancestry and persistence artifacts to find hosts that need incident response.
Camera service launched the scripts
Huntress traced the malicious activity to GeoStartupAgentService.exe. On exposed endpoints, the service spawned cmd.exe, which launched PowerShell to retrieve and run a first script from 45[.]32[.]117[.]34. Huntress labels the scripts a.ps1, b.ps1 and c.ps1. The first ran in memory, looked for writable directories and checked whether Microsoft Defender was active.
The second script was written to disk and run through WMI. It checked writable directories and downloaded kvckiller.sys. Huntress identifies that file as the vulnerable kernel driver wsftprm.sys, a driver previously abused in bring-your-own-vulnerable-driver attacks to tamper with antivirus. Huntress observed the download; check driver-load telemetry before concluding that a host ran the driver.
The attackers also set Image File Execution Options Debugger values for MsMpEng.exe, SecurityHealthService.exe and SecurityHealthSystray.exe. Windows uses those values to start a configured debugger when the named executable launches. Here the settings redirected launches to systray.exe, which Huntress assesses as a likely attempt to prevent the intended security components from starting. Inspect both the values and the actual state of Defender and Windows Security on a suspect host.
Loader kept returning for mining
The third script ran in memory and retrieved update.exe, a Go loader that contacted 156[.]246[.]94[.]183. At the time of Huntress’s investigation, that address was associated with cctv-update[.]top. The loader included a BitTorrent Mainline DHT client and a PKARR resolver. Those components can locate current server addresses using a public key, giving the operator another way to move infrastructure beyond the one domain.
On some hosts, update.exe created PackageUpdater to run C:\WINDOWS\system32\config\systemprofile\update.exe every 15 minutes; Huntress also saw PackageUpdater_Startup run at startup with SYSTEM privileges on some endpoints. The loader then downloaded the XMRig miner as ApplyUpdate.exe. A miner’s CPU load might bring attention to a server, but the recurring tasks and the altered security-process launches are more durable evidence of this intrusion.
Hunt for the parent process
Start with Windows process-creation telemetry for GeoStartupAgentService.exe spawning cmd.exe or PowerShell. Follow that lineage through WMI execution, update.exe and ApplyUpdate.exe. For the loader, Huntress lists SHA-256 f1235751c9e48e5732b7b183dc2bb175a19e4c6401dfd0e96b4cfdd0d8c54b4c; for the scripts it lists b673c4d707828abedc767a2be6badef7454492e62c37e30cf3cc5a402fd3647b. Its driver hash is ff5dbdcf6d7ae5d97b6f3ef412df0b977ba4a844c45b30ca78c0eeb2653d69a8. Match hashes to files or recorded file events, then retain the process tree and timeline.
Network observables from Huntress include the script host 45[.]32[.]117[.]34, loader contact 156[.]246[.]94[.]183 and possible exploitation source 2[.]59[.]133[.]151 seen with WebCamServer.exe. Huntress also suggests looking for unexpected DNS requests to the legitimate resolvers 8.8.8.8, 8.8.4.4 or 1.1.1.1 from a process other than the system DNS client, and outbound DHT traffic on UDP 6881 or similar from a GeoVision server. Those resolver addresses are shared services; evaluate them with the process identity and network context rather than blocking the services by address.
Restrict management and verify recovery
Remove unnecessary internet access to GeoVision devices and management interfaces. Put administration behind a VPN or allow only trusted IP addresses, as Huntress recommends. On a host with a matching process tree, IFEO Debugger value, task or malware hash, isolate the machine and preserve process, task, registry and network evidence before removing files or changing settings. Examine both PackageUpdater and PackageUpdater_Startup, and check whether MsMpEng.exe, SecurityHealthService.exe and SecurityHealthSystray.exe launch as intended after response.
From an external vantage point, verify that untrusted addresses can no longer reach the management interface. On rebuilt or remediated hosts, check that the two named tasks and suspect IFEO redirects are absent, Defender components launch normally, and process telemetry shows no new command shell under GeoStartupAgentService.exe. A quiet miner alert alone would miss the loader that brought it back every 15 minutes.