@lekzo/baileys
Affected
- introduced
0(semver)
Fixed versions
None listed
Fix
No fixed version is listed.
Advisory
Also known as: GHSA-jv7g-wqqq-m6gm
Malicious package Its source marks this package as malicious: it is not a vulnerability in a legitimate one.
Malicious code in @lekzo/baileys (npm)
---
_-= Per source details. Do not edit below this line.=-_
Source: amazon-inspector (da5caafea4a5656343feb4b52bf0007c98e6ed65a41ad22c79f24c0f1c48566f)
package.json declares the libsignal dependency as github:canove/libsignal-node — a bare GitHub owner/repo reference with no commit SHA, tag, or semver version. On npm install, this resolves to whatever the current HEAD of that third-party repository points at, fetching and installing arbitrary code with no integrity check and running any lifecycle scripts inside the returned bytes. Whoever controls that GitHub repository at any future moment controls code executed on every installer of this package. The static ping/GET co-occurrence in lib/Utils/generics.js is unrelated to this finding.
Source: ghsa-malware (f596dd408ac6057305a2459aa435aab72d3a914a4a1c24c66df927f065fafbdc)
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