MAL-2026-16483 Malicious code in @rixxcodex/baileys (npm)
Malicious package
Published
MAL-2026-16483 is a malicious package: @rixxcodex/baileys (npm). Every version was published to cause harm.
Task:
1. Search this repository's dependency manifests and lockfiles for the package, including transitive dependencies.
2. If it is present, remove it, regenerate the lockfile with the project's package manager, and replace whatever it was used for.
3. List any CI runners, developer machines or containers that installed it, so their secrets can be rotated.
4. If the package is not used anywhere, say so and change nothing.
Reference: https://insights.sbomify.com/MAL-2026-16483/ (Markdown: https://insights.sbomify.com/MAL-2026-16483/index.md)
- Package
- @rixxcodex/baileys
- Registry
- npm
What is MAL-2026-16483?
MAL-2026-16483 is a malicious package in @rixxcodex/baileys, published on 23 Sep 2026.
Official description
This package is a fork of the Baileys WhatsApp library that adds three undocumented channels which use the installer's authenticated WhatsApp session to perform account actions chosen by the author at runtime. In lib/Socket/socket.js around line 334, a base64-encoded URL decodes to https://raw.githubusercontent.com/skyzopedia/Screaper/refs/heads/main/idChannel.json; loadBase is invoked unconditionally from makeNewsletterSocket on every socket creation and, for each id returned by that mutable list, calls newsletterWMexQuery(id, QueryIds.FOLLOW) on the connected account. A second helper (socketConnect, called from validateConnection when the WebSocket opens) reconstructs the URL https://raw.githubusercontent.com/skyzopedia/NewsletterID/refs/heads/main/VIP_Push.json from a numeric char-code array (String.fromCharCode(…)) and, for each returned newsletter_id, issues a w:mex query with hardcoded query_id 7871414976211147 against the installer's session. A third helper, generateMessageV, is exposed on the socket API and, after a 40 second delay, invokes its callback with a hardcoded @newsletter JID obfuscated as a base64 blob XORed with the constant 23, again paired with query_id 7871414976211147. None of these behaviors are described in the README, and both remote lists are runtime-mutable by the author. In addition, package.json declares the cryptographic dependency "@rixxcodex/libsignal": "github:RixxCode/libsignal" with no tag or commit SHA, so npm install resolves whatever HEAD of that repository currently contains and executes it inside the Signal session-encryption path with no integrity check.
What should I do about MAL-2026-16483?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.