Malicious code in bazelisk (npm)
Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.
osv · MAL-2026-14227
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (d4bcbd35130e716d1a2940c91b6691d41b9655fdc8587404af37bc6e5a7f1370) 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.
- Source published
- 19 Aug 2026 03:41:01 UTC
- Source modified
- 19 Aug 2026 04:00:18 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- OSV · upstream source license applies
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.