MAL-2026-14227 Malicious code in bazelisk (npm)
Malicious package
Published
MAL-2026-14227 is a malicious package: bazelisk (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-14227/ (Markdown: https://insights.sbomify.com/MAL-2026-14227/index.md)
- Package
- bazelisk
- Registry
- npm
What is MAL-2026-14227?
MAL-2026-14227 is a malicious package in bazelisk, published on 19 Aug 2026.
Official description
This npm package uses the name
bazelisk, colliding with Google's bazelbuild/bazelisk project (referenced in the tarball's source.txt), and self-labels as a 'Security research canary'. Its postinstall script collects the installer's hostname, platform, arch, Node version, package name, and npm lifecycle event and POSTs that JSON payload to https://grqx3qve.instances.poc.jchunt.top/bazelisk at npm install time. The destination host is unrelated to the real bazelisk publisher. Installer host identifiers and environment fingerprint leave the machine automatically on install, matching a dependency-confusion beacon pattern.What should I do about MAL-2026-14227?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.