use-unsaved-changes (npm) · Malicious Code
Affects use-unsaved-changesSource GCVE Database
Malicious package : remove use-unsaved-changes and rotate any secrets on hosts that installed it.
Data as of 18 Nov 2026, 02:24 UTC
Malicious package
Published to npm · OSV MAL-2025-190941
What to do
Remove use-unsaved-changes 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 |
|---|---|---|
| npmuse-unsaved-changes | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package 'use-unsaved-changes' version 1.0.9 was found to contain malicious code. This malware, linked to the Sha1-Hulud: The Second Coming NPM worm, steals tokens and credentials and publishes them to GitHub. It propagates by infecting other NPM packages owned by the user and establishes persistence via a GitHub action. Additionally, it may destroy the user's home directory. Systems with this package installed should be considered fully compromised.
References
- github.com/advisories/GHSA-832j-xq5g-9xf4 (opens in a new tab)
- aikido.dev/blog/shai-hulud-strikes-again-hitting-zapier-ensdomains (opens in a new tab)
- wiz.io/blog/shai-hulud-2-0-ongoing-supply-chain-attack (opens in a new tab)
- stepsecurity.io/blog/sha1-hulud-the-second-coming-zapier-ens-domains-and-other-prominent-npm-packages-compromised (opens in a new tab)