@lendkzn/baileys
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-wv69-wpw9-p4x7
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @lendkzn/baileys (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (f1be48604bc03be61e45b7a38b0e9708c64b89d361c2799e9e8a393e2f1d5270)
package.json declares the dependency libsignal as an npm alias to @bellaxchuu/libsignal-node@latest, a different publisher's package pinned to the mutable latest dist-tag with no version constraint and no integrity hash. On npm install, resolution fetches whatever that alias currently points to, and the aliased package becomes a transitive code-execution dependency of this package (loaded at require time by the Baileys crypto path). The alias publisher does not match the package author, and the aliased name is unrelated to the upstream libsignal implementations commonly used by Baileys forks. This is an off-registry-style supply-chain redirection: control over the installed libsignal bytes is handed to a third party at every install.
Source: ghsa-malware (9eb771bdc7ee354aba17e83aa1aaa5da676920f7f8d095dd148f916880d0aa4b)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
Not rated by the source.
0 (semver)None 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