new-solt (npm) · Malicious Code
Affects new-soltSource GCVE Database
Malicious package : remove new-solt 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-6285
What to do
Remove new-solt 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-solt | 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 (d5a46a9516de2c87a2d451b78ace7033fb9dffa9faa4216b84eb068136098cfa) Package new-solt@0.0.8 contains index.js which imports child_process and invokes execSync with bash and zsh shell strings (around lines 315 and 331). Without further code-flow tracing it cannot be determined whether these shell calls are tied to install-time or import-time side effects, whether they execute attacker-controlled or fetched content, or whether they form part of a documented user-facing CLI. The pattern alone (child_process + shell execution) is consistent with both legitimate tooling and exfiltration/dropper behavior, so a human reviewer should examine the full execution path before installing or recommending this package. ## Source: ghsa-malware (0cb151695f19820479204dd7c0cc067a235aaffbb89340888bd79a39b8e6070c) 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.