Which versions of @chatunity/baileys are malicious?

The following npm versions of @chatunity/baileys are flagged malicious: 2.0.9, 3.2.0, 3.2.1. Treat any of these as compromised.

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

@chatunity/baileys is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — @chatunity/baileys is associated with the IN-MAL-2026-020676, IN-MAL-2026-020677, GHSA-2vxg-pmhf-2c8r, IN-MAL-2026-021468 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 @chatunity/baileys across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @chatunity/baileys (3 malicious versions).

Malicious package

@chatunity/baileysnpm

Advisory published Sep 29, 2026Updated Oct 13, 2026

@chatunity/baileys is a confirmed malicious npm package (MAL-2026-17287) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.9, 3.2.0, 3.2.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @chatunity/baileys (npm)

MAL-2026-17287

Immediate action

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

npm uninstall @chatunity/baileys

What this malware does

This package presents itself as a fork of the Baileys WhatsApp library. On every successful login through makeWASocket, lib/Socket/socket.js invokes autoSubscribeToDefaultNewsletterIfRequired(), which calls followNewsletterWMex with the hardcoded JID '120363418582531215@newsletter' — an author-controlled WhatsApp newsletter. The behavior is undocumented in the README, persists across sessions via a flag (basedbysam) stored in the credentials file, and uses the consumer's authenticated WhatsApp session to perform an account action (following a channel) without consent. Any bot or application built on top of this library will silently enroll its WhatsApp account as a follower of the author's channel. Additionally, package.json pins the critical libsignal cryptographic dependency to an unpinned GitHub branch (github:realvare/libsignal), meaning the owner of that repo can ship arbitrary crypto code to installers at any time without a version bump.

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

3 flagged

2.0.93.2.03.2.1

Indicators of compromise (SHA-256)

8f15bfd7bf2ef13da7abc8337b67a3f48091b256bdbf54396953f5eda6beb945

b6d06d6b516b21b0ac6ed45e5653dca243695a2c17326669ec58498e4c9bcf45

91f51e9df3ce8c75b411231fdaa15fe49a42b616a168e6c84363229c5519b40f

acc8739717b3768c51a56da3a23b85b253b0bc08a2ab4a447e278d055c8a2e70

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @chatunity/baileys (3 malicious versions).
If you installed it — respond
@chatunity/baileys is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @chatunity/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. @chatunity/baileys on npm has been identified as a malicious package (versions 2.0.9, 3.2.0, 3.2.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020676IN-MAL-2026-020677GHSA-2vxg-pmhf-2c8rIN-MAL-2026-021468

References

Credits

Amazon Inspector · finder
OX Security · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database