@chatbridgeworld/baileys@1.0.1
Malicious code in @chatbridgeworld/baileys (npm)
Analysis
Package @chatbridgeworld/baileys imitates the widely used @whiskeysockets/baileys library: it republishes a copy of that codebase under an unofficial scope while keeping the canonical package basename, and re-points the package's Signal-protocol dependency at a third-party repository. Version 1.0.1 declares "libsignal": "github:realvare/libsignal" and version 1.0.2 declares "libsignal": "github:chatbridgegit/libsignal-node"; upstream baileys uses WhiskeySockets/libsignal-node. Installing the package therefore clones and builds code from those unaffiliated GitHub accounts and runs that repository's lifecycle scripts with the installer's privileges, while the WhatsApp session material the library manages (auth_info/creds.json, Noise/identity keys) is processed by the substituted implementation. The two releases point at different accounts, and neither account is referenced in the package's own documentation. No second-stage beacon, encoder or network callback was found inside the published tarball itself; the preinstall hook (engine-requirements.js) is only a Node.js version check. Primary IOC: the dependency sources github[.]com/realvare/libsignal and github[.]com/chatbridgegit/libsignal-node.
- analyzed by
- Leitwacht
- first seen
- Nov 5, 2026, 06:05 PM
- analyzed
- Nov 5, 2026, 06:22 PM
- weekly installs
- 712
Related advisories
- @chatbridgeworld/baileys@0.0.0-stage same package
- @chatbridgeworld/baileys@1.0.2 same package
- @chatbridgeworld/baileys@1.0.0 same package
- teick@1.0.2
- @axo_cuy/baileyss@4.0.0
- @ruthless-imperium/baileys@1.0.3
- teick@1.0.1
- @denzz221/baileys@8.0.5
Independently detected by the Leitwacht supply-chain probe. IOCs are defanged. Published CC0. Think this is a mistake? See the dispute policy.