Which versions of @nexustechpro/baileys are malicious?

The following npm versions of @nexustechpro/baileys are flagged malicious: 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 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 @nexustechpro/baileys part of a known attack campaign?

Yes — @nexustechpro/baileys is associated with the IN-MAL-2026-019904 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?

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

Malicious package

@nexustechpro/baileysnpm

@nexustechpro/baileys is a confirmed malicious npm package (MAL-2026-16104) that steals credentials and exfiltrates sensitive data (malicious version 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 WhatsApp library baileys in which lib/Socket/chats.js (~270 KB) is heavily obfuscated (obfuscator.io-style rotating string-array decoder, hex-escaped import specifiers such as '\x40\x63\x61\x63\x68\x65\x61\x62\x6c\x65\x2f\x6e\x6f\x64\x65\x2d\x63\x61\x63\x68\x65', integer-arithmetic control flow, unicode identifier names, ~2772-entry string array) while every sibling file in lib/Socket/ (groups.js, messages-recv.js, socket.js, registration.js) remains readable JavaScript and the upstream whiskeysockets/baileys ships this file unobfuscated. The obfuscated module is reachable from the package entry point (lib/index.js) and sits directly in the code path that handles WhatsApp session state (authState credentials, Signal identity keys, noise keys, signed pre-keys). package.json additionally declares "whatsapp-rust-bridge": "latest", a floating unpinned tag on a non-upstream dependency, which allows that dependency's publisher to ship arbitrary code (including install lifecycle scripts) into every installer of this package on any future install with no version pin or integrity check.

Malicious versions

1 flagged

2.2.7

Indicators of compromise (SHA-256)

fed8b2b0be012012aa9b1716e58c6d9e9a7302e431d5f8945e7b1196b6d7afab

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @nexustechpro/baileys (version 2.2.7). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @nexustechpro/baileys across your stack and pipelines.
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 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 @nexustechpro/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. @nexustechpro/baileys on npm has been identified as a malicious package (version 2.2.7 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-019904

References

npmjs.com

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