Which versions of @lekzo/baileys are malicious?

The following npm versions of @lekzo/baileys are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate @lekzo/baileys if I installed it?

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.

I already installed @lekzo/baileys — how do I know if it already compromised me?

If @lekzo/baileys was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @lekzo/baileys part of a known attack campaign?

Yes — @lekzo/baileys is associated with the IN-MAL-2026-020172 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @lekzo/baileys across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @lekzo/baileys (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @lekzo/baileys across your stack and pipelines.

Malicious package

@lekzo/baileysnpm

@lekzo/baileys is a confirmed malicious npm package (MAL-2026-16276) that executes malicious code on install (malicious version 0.0.1). 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 with no tag, branch, or commit SHA. On npm install, npm fetches whatever the default branch HEAD of that repository currently points to and runs any lifecycle scripts inside the fetched tree, with no version resolution against the npm registry and no integrity check. The bytes that execute on the installer's machine are entirely controlled by whoever holds write access to that GitHub repo at install time and can change silently between installs.

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2cd9141ef0d6d97338c5f976c8071a6f5c37010683b27d4463b2221d76b82304

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @lekzo/baileys (version 0.0.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @lekzo/baileys across your stack and pipelines.
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.
Did it already run?
If @lekzo/baileys was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @lekzo/baileys before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

IN-MAL-2026-020172

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database