Which versions of test-dev-sync are malicious?

The following npm versions of test-dev-sync are flagged malicious: 0.1.0. Treat any of these as compromised.

How do I remediate test-dev-sync if I installed it?

test-dev-sync is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed test-dev-sync — how do I know if it already compromised me?

If test-dev-sync was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is test-dev-sync part of a known attack campaign?

Yes — test-dev-sync is associated with the GHSA-c2gc-7pfc-7fjf, IN-MAL-2026-011048 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find test-dev-sync across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for test-dev-sync (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-dev-sync across your stack and pipelines.

Malicious package

test-dev-syncnpm

test-dev-sync is a confirmed malicious npm package (MAL-2026-11494) that steals credentials and exfiltrates sensitive data (malicious version 0.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in test-dev-sync (npm)

MAL-2026-11494

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall test-dev-sync

What this malware does

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.

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.

Malicious versions

1 flagged

0.1.0

Indicators of compromise (SHA-256)

08d84ffac131c96846518a7d31bd752bf3e3f87cad1e79383458b24f489d0140

b79a278016b87011ec1e810ce455d87ab6346a1045cc007e0155b204c8cc2532

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for test-dev-sync (version 0.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging test-dev-sync across your stack and pipelines.
If you installed it — respond
test-dev-sync is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If test-dev-sync was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks test-dev-sync before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. test-dev-sync on npm has been identified as a malicious package (version 0.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-c2gc-7pfc-7fjfIN-MAL-2026-011048

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks test-dev-sync-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database