Which versions of use-unsaved-changes are malicious?

The following npm versions of use-unsaved-changes are flagged malicious: 1.0.9. Treat any of these as compromised.

How do I remediate use-unsaved-changes if I installed it?

use-unsaved-changes is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed use-unsaved-changes — how do I know if it already compromised me?

If use-unsaved-changes was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is use-unsaved-changes part of a known attack campaign?

Yes — use-unsaved-changes is associated with the GHSA-832j-xq5g-9xf4 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find use-unsaved-changes across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for use-unsaved-changes (version 1.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging use-unsaved-changes across your stack and pipelines.

Malicious package

use-unsaved-changesnpm

Malicious code in use-unsaved-changes (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190941

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall use-unsaved-changes

What this malware does

The package use-unsaved-changes was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.0.9

Indicators of compromise (SHA-256)

4ad4c18a29610889faeb6880a6633da79b74fc78f8427b6eae436de1a3198bfc

96deeb533a3de753f2de9201e46a0a8ccfa79d22d848ed8cbb20f19b36242ae6

f8514afe43298a9aa750c9e11b5b001c7349e82474c204ce27a468af3eb7f393

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for use-unsaved-changes (version 1.0.9). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging use-unsaved-changes across your stack and pipelines.
If you installed it — respond
use-unsaved-changes is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If use-unsaved-changes was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks use-unsaved-changes before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. use-unsaved-changes on npm has been identified as a malicious package (version 1.0.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-832j-xq5g-9xf4

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks use-unsaved-changes-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring