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.

Source published

18 Sep 2026 01:40:17 UTC

Source modified

12 Oct 2026 15:45:05 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.