@lendxntaa/baileys

This package is part of a large family (100+ identified as of September 2026) of near-identical forks of the Baileys WhatsApp Web library that inject a covert channel-subscription action into the WhatsApp socket layer. On connect, the injected code issues an authenticated `w:mex` FOLLOW query (query_id 7871414976211147) against one or more attacker-chosen WhatsApp Channel/Newsletter JIDs, using the installer's own authenticated WhatsApp session -- silently subscribing the victim's account to channels it never asked to join. The target JID(s) are hidden from casual source review via one of several obfuscation techniques observed across the family: a plain string literal, base64 encoding, base64+XOR, or a char-code array reconstructed at runtime. Some variants instead fetch a mutable, attacker-controlled remote JSON/JS list of target JIDs from GitHub or another host at runtime, letting the target list change after installation without a new npm publish. Every sample in the family shares the same underlying mechanism (a wrapped/patched socket-connect routine that fires the FOLLOW query some seconds after connect), even though the package name, JID value(s), and obfuscation/delivery method differ per fork. The malicious action abuses the installer's own authenticated WhatsApp session to gain reach and subscribers for attacker-controlled channels; it does not exfiltrate credentials, establish persistence, or execute arbitrary remote code. Affected package: @lendxntaa/baileys (npm), version(s): 9.5.0, 9.3.0, 9.1.0, 9.0.2, 9.0.1. --- ## Source: amazon-inspector (0f844237b0db70e56f303c5780ea3a9bd92ae29696bb299ca739961fbc1422a0) @lendxntaa/baileys is a fork of the Baileys WhatsApp client that declares `"libsignal": "npm:@bellaxchuu/libsignal-node@latest"` in package.json. The `libsignal` module id is loaded on the crypto/signal path of the WhatsApp client, so `require('libsignal')` inside this package resolves to code published under the unrelated `@bellaxchuu` scope, pinned to the mutable `latest` tag with no version and no integrity metadata. Every `npm install` can resolve to different bytes chosen by whoever controls that scope, and those bytes execute in-process whenever a consumer of this package uses the WA client. Package metadata further reduces reviewability: `homepage` and `repository.url` both point at a Telegram channel (`https://t.me/lendd3`) rather than a source repository, and the tarball ships a ~130 KB `lib/antiban.js` bundle not present in upstream Baileys. ## Source: ghsa-malware (7ee7bfa4e96d338ab7d8a6762a9f758218f34953d934bb86cd5321dfbe03fd68) 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.