new-solt-1 (npm) · Malicious Code
Affects new-solt-1Source GCVE Database
Malicious package : remove new-solt-1 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-6286
What to do
Remove new-solt-1 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-1 | 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 (51a48524931e3ec3199917bed8d48e70c07bf91f4a0322a46926b7c1d98d8b3e) index.js imports child_process and invokes execSync with bash and zsh shells (around lines 315 and 331). The shell-execution pattern alone is not conclusive of malicious intent — it can appear in legitimate developer tooling, build helpers, or CLI utilities — but the package name has no clear declared purpose and the shell-execution surface warrants human inspection of the actual command strings, their inputs, and the trigger context (lifecycle hook vs. explicit CLI invocation) before recommending the package to installers. ## Source: ghsa-malware (548ecaba7e63993f2d3c88cfb13098ae8b6c69161e2e748bd8b931dcbaec8c7b) 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.