Which versions of @bil-rgb/baileys are malicious?

The following npm versions of @bil-rgb/baileys are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate @bil-rgb/baileys if I installed it?

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

If @bil-rgb/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.

Is @bil-rgb/baileys part of a known attack campaign?

Yes — @bil-rgb/baileys is associated with the IN-MAL-2026-022476, IN-MAL-2026-022475 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 @bil-rgb/baileys across my projects, lockfiles, and CI pipelines?

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

Malicious package

@bil-rgb/baileysnpm

Advisory published Nov 2, 2026Updated Nov 2, 2026

@bil-rgb/baileys is a confirmed malicious npm package (MAL-2026-18441) that executes malicious code on install (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @bil-rgb/baileys (npm)

MAL-2026-18441

Immediate action

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

npm uninstall @bil-rgb/baileys

What this malware does

package.json for @bil-rgb/[email protected] declares its libsignal dependency as github:tenka-san/libsignal-node with no commit SHA, no tag, and no integrity check. npm install resolves this value by cloning whatever currently exists at HEAD of that personal GitHub user's repository and running any lifecycle scripts contained in it. The resolution target is a personal user account unrelated to the upstream signalapp/libsignal-node or WhiskeySockets Baileys publisher, so the code that executes on an installer's machine at install time is whatever that account chooses to place in the referenced branch at the moment of install, independent of this package's own tarball contents. The remainder of the package body (lib/Utils/generics.js and surrounding files) is a Baileys fork; the install-time attacker control is produced by the manifest line itself.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

3bcbf6493a6aa37ccc827723d6fd73b082c66d10a549af2413aba2a8a6f47b7f

748ce601bf34ec5b40cccc2c1642cff8df916ebab398bf08aebbe84f7adae1ef

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @bil-rgb/baileys (2 malicious versions).
If you installed it — respond
Remove @bil-rgb/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 @bil-rgb/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. @bil-rgb/baileys on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-022476IN-MAL-2026-022475

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @bil-rgb/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