new-helper (npm) · Malicious Code
Affects new-helperSource GCVE Database
Malicious package : remove new-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-6284
What to do
Remove new-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 |
|---|---|---|
| npmnew-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 (47f6e9bcab53d95265012a31a4dcfc1485ed6db858e788e68ac2ac1ebc33fc34) index.js imports child_process and contains execSync calls invoking bash and zsh (around lines 301 and 317). Without traced execution context, it is not possible to determine whether these calls are reachable at install/import time, whether they execute attacker-controlled content, or whether they are gated behind explicit user CLI invocation. No hardcoded attacker C2, credential-path reads, or known-bad-infrastructure fingerprints are present in the available evidence. Routing to human review to inspect the surrounding code paths and confirm intent. ## Source: ghsa-malware (cabb68bd9f2c4312904814f7c0c11aae7f93772a5c46c28a1ca8292592c83a53) 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.