Skip to content

Vulnerabilities & Patches

Huntress traces multiple intrusions to compromised camera management application

Huntress said the camera management software's vendor remains unidentified and that attackers used a reverse shell and sideloaded DLLs.

https://breach-signal.com/vulnerabilities/huntress-traces-camera-management-app-intrusions/

Share

Key facts

  • Security firm Huntress traced multiple intrusions from September and October 2026 to a compromised camera management application used as an initial-access vector into corporate networks.
  • Huntress analysts could not determine the full name, creator, or vendor of the camera management software.
  • CMS.exe launched rs.win32.exe, which functioned as a reverse shell.
  • Attackers dropped a copy of legitimate Microsoft file WpcMon.exe into AppData\Local\Microsoft\WpcMon rather than the expected Windows system directory.

Huntress traced a series of intrusions from September and October 2026 back to a compromised camera management application that attackers used as an initial-access vector, or first foothold, into corporate networks. Huntress said the application appeared as CMS.exe, an executable — a file that runs a program.

Huntress said the software’s full name, creator, and vendor were never identified. The application left no logs behind, so Huntress’s analysts could not determine how the compromise happened. Huntress found a CMS package offered for download on kvision[.]ai that shared strings and a web address with the malicious executable, but the firm called kvision[.]ai a possible source only, never a confirmed vendor connection.

Huntress said attackers placed rs.win32.exe in the user’s AppData\Roaming\CMS\RemoteSetup folder (AppData folders are user-writable locations in a Windows user profile), and CMS.exe launched the file. The file functioned as a reverse shell, which lets an attacker remotely control the compromised machine.

Huntress said the reverse shell launched from a command line on port 8000, a network port that routes traffic to a specific service, supplying the admin username together with the password 1234567a7654321. Huntress also found strings inside CMS.exe, including developerslavery, d3e3v4e3l9o9p0e3r4s2l9a1v4e3r4y6, and hxxp://cloudapi.3r-dataware[.]com/sso/. The domain 3r-dataware[.]com is tied to a Korean company named 3R Global.

Huntress said attackers dropped a copy of the legitimate Microsoft file WpcMon.exe into AppData\Local\Microsoft\WpcMon instead of the expected Windows system folder. WpcMon.exe sideloaded malicious DLLs — dynamic-link libraries loaded at runtime by a trusted program — named IPHLPAPI.DLL and samcli.dll, presented as legitimate zlib compression libraries, a data-compression library. Sideloading loads a malicious library alongside a trusted executable so the trusted file runs the attacker’s code.

Huntress said attackers had altered the DLLs to add beaconing functionality — repeated check-ins to a command-and-control server, the attacker-controlled machine that receives beacons and issues instructions — and to periodically contact that server. Huntress confirmed through a SHA256 hash, a cryptographic fingerprint that identifies a file, that the dropped copy is Microsoft’s legitimate Windows Parental Control Monitor file, a Windows parental-control component.

Huntress said threat actors added a registry value inside the user’s personal Run key — the registry location that starts programs at sign-in — pointing to WpcMon.exe, which made the malicious code launch at every sign-in. Every incident pointed to the same command-and-control server address, 144.172.116[.]37. CMS.exe, the malicious executable, came without an embedded File Version Information section, the version metadata Windows stores inside executable files.

Huntress said organizations should treat camera management tools as potential entry points into corporate networks. Defenders should inventory the software, restrict access to it, and watch for unusual processes and connections heading out of the network, especially from folders users can write to.

Huntress also urges defenders to deploy application control — technology that allows only approved executables and DLLs to run — so unapproved programs cannot launch from user-writable directories such as AppData folders. Teams should trace how CMS.exe led to rs.win32.exe, how rs.win32.exe tied to atypical WpcMon.exe behavior, and where unauthorized connections left the network. The chain links one compromised management tool to broader access inside corporate networks.

Huntress said defenders usually prioritize the software attackers are known to target, yet weaknesses can hide in any software reaching into an environment, including tools outside the usual attack surface. That gap means tools such as camera management software can go under-patched and overlooked, even though such software touches the environment.

Was this helpful?

Join the discussion

Please read our Comment Policy before commenting. First-time comments are held for moderation. By posting a comment you agree to our Terms of Use and Privacy Policy, which explain how your name, email address and comment are used.

Your email address will not be published. Required fields are marked *