parket-flow (npm) · Malicious Code
Affects parket-flowSource GCVE Database
Malicious package : remove parket-flow 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-6334
What to do
Remove parket-flow 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-flow | 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 (8e9b185a1b54e41a8fb900a67aab43dbb78abc4fea96e9ca05d356f6864e3bdd) index.js imports child_process and invokes execSync with bash and zsh shells (index.js line 1, 301, 317). Without traced execution context it is not possible to determine whether these shell invocations are part of legitimate tool functionality or whether they fetch and execute attacker-controlled content. No corroborating evidence of exfiltration, credential access, network beacons, or attacker-controlled endpoints is present in what was inspected. Recommend human review of the shell command construction and any inputs they consume before allowing or blocking. ## Source: ghsa-malware (4a16b4d37e2525d236562aba3e3562dd73f016e89f417ebead9c82dcbb668d85) 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.