@xzvbailss/baileys@6.0.0
Malicious code in @xzvbailss/baileys (npm)
Analysis
This package is an unofficial republication of the WhatsApp library @whiskeysockets/baileys, shipped under the unrelated scope @xzvbailss and declaring itself as the same library ("a Baileys-based Wazapp Web library"), with its repository and homepage fields pointing at Telegram channels (t[.]me/XzRzSynxC, t[.]me/JustRxVz) rather than source control. It differs from the upstream project in ways an installer would not expect: its preinstall hook runs `node ./engine-requirements.js`; crypto primitives are delegated to third-party packages instead of the upstream implementations — `whatsapp-rust-bridge@0.5.4` provides hkdf/md5 (lib/Utils/crypto.js), expandAppStateKeys (lib/Utils/chat-utils.js) and LTHashAntiTampening (lib/Utils/lt-hash.js), and libsignal is pulled from the personal repository github:tenka-san/libsignal-node; and lib/Socket/luxu.js hardcodes WhatsApp channel identifiers ("120363421563597486@newsletter" / "PouCode", "120363399602691477@newsletter", and "0@newsletter" labelled "WhatsApp" / sender "7-Yuukey") which it injects as forwardedNewsletterMessageInfo on every generated album, event and poll-result message, promoting those channels through messages sent by any application using the library. lib/index.js also prints Telegram channel links on import. No network C2 endpoint, credential access, or obfuscated payload was found in the shipped code.
- analyzed by
- Leitwacht
- first seen
- Nov 11, 2026, 10:20 PM
- analyzed
- Nov 11, 2026, 10:21 PM
- weekly installs
- 695
Related advisories
- @xzvbailss/baileys@6.0.8 same package
- @xzvbailss/baileys@6.0.5 same package
- @xzvbailss/baileys@5.0.0 same package
- @xzvbailss/baileys@1.0.0 same package
- @zlynzee/baileys@1.0.6
- @skycodee/baileys@8.0.8
- @langitdeveloper/baileys@2.2.1
- @daffadevv/baileys@1.0.0
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.