Which versions of nanoreset are malicious?

The following npm versions of nanoreset are flagged malicious: 7.0.1, 7.0.2. Treat any of these as compromised.

How do I remediate nanoreset if I installed it?

nanoreset 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 nanoreset — how do I know if it already compromised me?

If nanoreset 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 nanoreset part of a known attack campaign?

Yes — nanoreset is associated with the GHSA-jhpm-rxq6-p8vc 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 nanoreset 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 nanoreset (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nanoreset across your stack and pipelines.

Malicious package

nanoresetnpm

Malicious code in nanoreset (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-190978

Immediate action

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

npm uninstall nanoreset

What this malware does

The package nanoreset 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

2 flagged

7.0.17.0.2

Indicators of compromise (SHA-256)

fc12f8a503d7dbf0bae6b335d8ea61ae3e1c8e6ec42e415cc48b4ab536180c8e

5d98d973ab73f5753f101bf681c2916dd61b81ae036a3519f76e17321ba9e2ef

bdb21b864a3ac0ba618209f022c32d24378cbb259ae7410692ca1db53f8ee721

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 nanoreset (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging nanoreset across your stack and pipelines.
If you installed it — respond
nanoreset 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 nanoreset 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 nanoreset 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. nanoreset on npm has been identified as a malicious package (versions 7.0.1, 7.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-jhpm-rxq6-p8vc

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nanoreset-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