{"id":"MAL-2026-14227","revision":"67532864e77b425bb20dd97fe4c50633","records":[{"revision":"67532864e77b425bb20dd97fe4c50633","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14227","aliases":[],"title":"Malicious code in bazelisk (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (d4bcbd35130e716d1a2940c91b6691d41b9655fdc8587404af37bc6e5a7f1370)\nThis 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.\n","state":0,"publishedAt":"2026-08-19T03:41:01+00:00","modifiedAt":"2026-08-19T04:00:18.2572131+00:00","affected":[{"ecosystem":"npm","name":"bazelisk","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/bazelisk/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14227","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14227","identifiers":["MAL-2026-14227"]},"retained":false,"historicalAffected":[]}],"coverage":[]}