parket-helper (npm) · Malicious Code
Affects parket-helperSource GCVE Database
Malicious package : remove parket-helper and rotate any secrets on hosts that installed it.
Data as of 11 Jul 2026, 09:43 UTC
Malicious package
Published to npm · OSV MAL-2026-6119
What to do
Remove parket-helper from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmparket-helper | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (31d62a38af75a45a91e590e0cffe4f58e900fe726b4323af1e481118d146277c) 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. ## Source: ghsa-malware (06da7444904a584b820efa9d1b6b7c8058d4f6f7495c344e354748992366e737) 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.