Which versions of parket-helper are malicious?

The following npm versions of parket-helper are flagged malicious: 0.0.1, 5.8.1. Treat any of these as compromised.

How do I remediate parket-helper if I installed it?

parket-helper 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 parket-helper — how do I know if it already compromised me?

If parket-helper 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 parket-helper part of a known attack campaign?

Yes — parket-helper is associated with the GHSA-w6cg-2gpv-j66m, IN-MAL-2026-008152, IN-MAL-2026-009463 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 parket-helper 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 parket-helper (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging parket-helper across your stack and pipelines.

Malicious package

parket-helpernpm

parket-helper is a confirmed malicious npm package (MAL-2026-6119) that steals credentials and exfiltrates sensitive data (malicious versions 0.0.1, 5.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in parket-helper (npm)

MAL-2026-6119

Immediate action

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

npm uninstall parket-helper

What this malware does

index.js imports child_process and invokes execSync with bash and zsh shells (lines 315 and 331). Without traced reachability, it is not established whether these calls fire at install/require time, fetch external content, or process attacker-controlled input. Helper packages that shell out can be legitimate (build tooling, environment setup) or harmful (droppers, env exfiltration), and the difference depends on what those execSync calls run and when. Manual review of index.js around the cited lines is recommended to determine the trigger context and the command strings being executed.

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

2 flagged

0.0.15.8.1

Indicators of compromise (SHA-256)

06da7444904a584b820efa9d1b6b7c8058d4f6f7495c344e354748992366e737

31d62a38af75a45a91e590e0cffe4f58e900fe726b4323af1e481118d146277c

6afc073d61198e24ae823e3c06dbff038cd9e05eeb9cd6e31f26fb7364edd97c

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 parket-helper (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging parket-helper across your stack and pipelines.
If you installed it — respond
parket-helper 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 parket-helper 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 parket-helper 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. parket-helper on npm has been identified as a malicious package (versions 0.0.1, 5.8.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-w6cg-2gpv-j66mIN-MAL-2026-008152IN-MAL-2026-009463

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks parket-helper-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