MAL-2026-5786 Malicious code in @solana-labs/ancor (npm)
Malicious package
Published
MAL-2026-5786 is a malicious package: @solana-labs/ancor (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-5786/ (Markdown: https://insights.sbomify.com/MAL-2026-5786/index.md)
- Package
- @solana-labs/ancor
- Registry
- npm
What is MAL-2026-5786?
MAL-2026-5786 is a malicious package in @solana-labs/ancor, published on 15 Jun 2026.
Official description
Package is published as
@solana-labs/ancor — a name one character off from anchor, the well-known Solana smart-contract framework (published as @coral-xyz/anchor, formerly @project-serum/anchor). The @solana-labs scope and the near-miss spelling ancor together create high confusion potential for developers searching for the Anchor framework. The shipped bundles lib/index.cjs.js and lib/index.esm.js are large minified rollups (~11k+ lines) that include require('child_process'), fetch(...) POST calls, and references to curl / ping. Pattern matches on keyword co-occurrence in a minified bundle do not by themselves prove malicious intent — Anchor and similar frameworks legitimately bundle child_process and HTTP for build/CLI tooling — but the combination of a typosquat-shaped name, a vendor-impersonating scope, and a large opaque bundle warrants human review before this version is allowed into installer environments. A reviewer should verify scope ownership (is @solana-labs actually controlled by Solana Labs, or a squatted scope?), de-minify the flagged regions around lines 5016/5046 and 11336/11441 to confirm whether the POST/fetch destinations and child_process spawns are part of a documented build/CLI flow or an exfiltration path, and compare bundle behavior against legitimate @coral-xyz/anchor.What should I do about MAL-2026-5786?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.
Sources
Also known as GHSA-h2x5-cj9x-hvcc.