NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@lekzo/baileysnpm

Advisory published Updated

@lekzo/baileys is a confirmed malicious npm package (MAL-2026-16276) that executes malicious code on install (malicious versions 0.0.1, 0.0.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @lekzo/baileys (npm)

MAL-2026-16276
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @lekzo/baileys

What this malware does

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.

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.

Malicious versions

2 flagged
0.0.10.0.7

Indicators of compromise (SHA-256)

2cd9141ef0d6d97338c5f976c8071a6f5c37010683b27d4463b2221d76b82304
da5caafea4a5656343feb4b52bf0007c98e6ed65a41ad22c79f24c0f1c48566f
f596dd408ac6057305a2459aa435aab72d3a914a4a1c24c66df927f065fafbdc

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @lekzo/baileys (2 malicious versions).

  2. If you installed it — respond

    Remove @lekzo/baileys from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @lekzo/baileys was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @lekzo/baileys on npm has been identified as a malicious package (versions 0.0.1, 0.0.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020172IN-MAL-2026-020316GHSA-jv7g-wqqq-m6gm

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @lekzo/baileys-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Explore

@lekzo/baileys (npm) malicious package — MAL-2026-16276 | O3 Security