Skip to content
OpenAdvisories
Malicious MAL-2026-11494 GHSA-c2gc-7pfc-7fjf

test-dev-sync

npm package · versions 0.1.0

Reported Aug 1, 2026 · Updated Aug 4, 2026

If this package is installed

Remove it, treat the machine (or CI runner) as compromised, and rotate every secret, token and key it could access — from a different, clean machine.

Details

Source: amazon-inspector (b79a278016b87011ec1e810ce455d87ab6346a1045cc007e0155b204c8cc2532)
test-dev-sync is a browser data stealer coupled to a remote-command backdoor. grabber_user.js enumerates Chrome/Chromium/Opera/Vivaldi profiles under LOCALAPPDATA and copies extension Local/Sync settings, Local Storage LevelDB, and the LastPass extension database; the collected tree is zipped and uploaded, keyed by a hardware fingerprint, through a sibling package's uploadFileToPublicApi sink. extproc.js additionally reads each profile's Secure Preferences JSON, derives a seed hash from resources.pak, collects the host SID via powershell, and uploads the resulting extinfo blob to the same sink. handleInstallExtension listens on a channel provided by the sibling test-dev-link, receives operator messages carrying an extension ZIP, unzips it into the Chrome User Data Extensions directory, terminates chrome.exe, rewrites Secure Preferences to authorize the planted extensions, adds HKCU\Software\Policies\Google\Chrome entries that disable developer-mode and extension restrictions, and relaunches Chrome with --restore-last-session, giving persistent operator control of the victim's browser. The package is presented under a generic "dev sync" name and splits its capabilities across sibling packages test-dev-config, test-dev-link, and test-dev-store, which supply the C2 channel, hardware fingerprint, and upload endpoint.

Source: ghsa-malware (08d84ffac131c96846518a7d31bd752bf3e3f87cad1e79383458b24f489d0140)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.