Which versions of zero-baileys are malicious?

The following npm versions of zero-baileys are flagged malicious: 2.7.0. Treat any of these as compromised.

How do I remediate zero-baileys if I installed it?

Remove zero-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 zero-baileys — how do I know if it already compromised me?

If zero-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 zero-baileys part of a known attack campaign?

Yes — zero-baileys is associated with the IN-MAL-2026-020174 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 zero-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 zero-baileys (version 2.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zero-baileys across your stack and pipelines.

Malicious package

zero-baileysnpm

zero-baileys is a confirmed malicious npm package (MAL-2026-16280) that executes malicious code on install (malicious version 2.7.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zero-baileys (npm)

MAL-2026-16280

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall zero-baileys

What this malware does

package.json redirects the libsignal dependency to npm:@otaxayun/libsignal-node@latest. The @latest dist-tag is mutable and unpinned, so each npm install of zero-baileys resolves whatever tarball the @otaxayun scope currently publishes and executes any lifecycle scripts (preinstall/install/postinstall) it contains. Upstream Baileys resolves libsignal from a pinned source; the alias here substitutes an unofficial third-party scope as the trust root for a core cryptographic dependency, with no version pin and no integrity check. The static match on child_process + https.request + POST in lib/Utils/messages-media.js:28 corresponds to media-download helpers in the runtime library and is not itself an install-time exfil path.

Malicious versions

1 flagged

2.7.0

Indicators of compromise (SHA-256)

58d472a4390be835fc8ffd5e62a7d3b2bb7270ad6ea651d9cd15bc7abd7735c8

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 zero-baileys (version 2.7.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging zero-baileys across your stack and pipelines.
If you installed it — respond
Remove zero-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 zero-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 zero-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. zero-baileys on npm has been identified as a malicious package (version 2.7.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020174

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks zero-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