bazelisk
Affected
- Versions:
1.0.0
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: None
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in bazelisk (npm)
---
_-= 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.
Not rated by the source.
1.0.0None listed
No fixed version is listed.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: OpenSSF Malicious Packages · Apache-2.0