@LENDKZN/BAILEYS · GHSA-wv69-wpw9-p4x7 · Package
UNINSTALL IT, ROTATE THE KEYS IT COULD READ
Not triaged yet. The sources’ own description is below.
first public Nov 16, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Unknown from the sources.
Unknown from the sources.
-= Per source details. Do not edit below this line.=-
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.
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.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.