Which versions of @nexustechpro/baileys are malicious?

The following npm versions of @nexustechpro/baileys are flagged malicious: 2.2.4, 2.2.5, 2.2.7. Treat any of these as compromised.

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

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

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

Yes — @nexustechpro/baileys is associated with the IN-MAL-2026-019904, GHSA-8w6v-4xp9-rvrr, IN-MAL-2026-021466, IN-MAL-2026-021467 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 @nexustechpro/baileys across my projects, lockfiles, and CI pipelines?

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

Malicious package

@nexustechpro/baileysnpm

Advisory published Sep 9, 2026Updated Oct 13, 2026

@nexustechpro/baileys is a confirmed malicious npm package (MAL-2026-16104) that steals credentials and exfiltrates sensitive data (malicious versions 2.2.4, 2.2.5, 2.2.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @nexustechpro/baileys (npm)

MAL-2026-16104

Immediate action

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

npm uninstall @nexustechpro/baileys

What this malware does

@nexustechpro/baileys is a fork of the Baileys WhatsApp library in which lib/Socket/chats.js (~270 KB) is transformed with obfuscator.io (large string-array with rotate loop, decoder wrapper, hex-escaped identifiers) while every other module under lib/Socket/ is plain, readable code matching upstream. The obfuscated module is re-exported from lib/Socket/index.js and therefore loads on every require() of the package, executing inside a socket chain that has access to the authenticated WhatsApp session credentials, contact list, and message stream. In addition, on every 'connection.update' where connection==='open', the package silently subscribes the installer's authenticated WhatsApp account to a hardcoded newsletter JID (120363422827915475@newsletter) and re-applies the subscription every 30 seconds via setInterval; an AUTO_FOLLOW_FORCE_MODE flag bypasses the already-following check so a user-initiated unfollow is undone. There is no configuration surface, opt-out, or documentation for this behavior. package.json also declares an unpinned first-party-sounding dependency 'whatsapp-rust-bridge: latest'. The package name and keywords mirror the upstream @whiskeysockets/baileys ecosystem.

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.2.42.2.52.2.7

Indicators of compromise (SHA-256)

fed8b2b0be012012aa9b1716e58c6d9e9a7302e431d5f8945e7b1196b6d7afab

540ddb6572705d776d96d9199b385b55b45093ea3f9da298751ae13c289d924d

77e10f9b682c7a34a63468b31a47d982a98bf6d0308b5dbe96b0df7bdb51fdd6

f36bbd92f268ccdeec610b1494add9a0bda52f78162c47d0666cc6aa12dcdad2

Detection & response playbook

Credential / info stealer

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

Campaign

IN-MAL-2026-019904GHSA-8w6v-4xp9-rvrrIN-MAL-2026-021466IN-MAL-2026-021467

References

Credits

Amazon Inspector · finder

Detect & block this

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