xzvbailey
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 xzvbailey (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (f961ec09baa139430fb2b04c3fef5350f16f659c8de585787a26f3c8535fca38)
package.json declares the libsignal dependency as github:tenka-san/libsignal-node, a non-registry source pointing at a personal GitHub account with no tag or commit SHA. On npm install, npm fetches whatever the default branch's HEAD points to at that moment and runs any lifecycle scripts inside the cloned repo, so the owner of that account controls code that executes on the installer's machine. The account is unrelated to the upstream Baileys/libsignal publishers, and the package's own metadata is inconsistent (homepage and repository fields point at a Telegram URL while the bug tracker points at a different GitHub org, pou-code/Baileys), which is consistent with a repackaged Baileys lure rather than a legitimate fork.
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