MAL-2026-13929 Malicious code in @dgxeon13/libsignal-node (npm)
Malicious package
Published
MAL-2026-13929 is a malicious package: @dgxeon13/libsignal-node (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-13929/ (Markdown: https://insights.sbomify.com/MAL-2026-13929/index.md)
- Package
- @dgxeon13/libsignal-node
- Registry
- npm
What is MAL-2026-13929?
MAL-2026-13929 is a malicious package in @dgxeon13/libsignal-node, published on 10 Aug 2026.
Official description
npm/@dgxeon13/libsignal-node impersonates Signal's libsignal Node binding. On require of index.js, after a short delay it runs install.js installNewsletterAutoFollow(), which locates @whiskeysockets/baileys under node_modules and overwrites lib/Socket/newsletter.js with an embedded payload that performs remote-controlled consentless WhatsApp newsletter auto-follow (fetch DGXeon13/strings after 120s, silent FOLLOW). This is supply-chain tampering of a third-party package at import time. Distinct from the separately reported @dgxeon/libsignal-node (different npm scope). Used as the libsignal alias from @dreamguyxeon/baileyx. Related campaign OSV: MAL-2026-2252, MAL-2025-806. Tarball sha256: 46e4b9fd62489e1e28c88f8ebac77cf0fa6c48639cd6d548bdb097ca6793d157.
What should I do about MAL-2026-13929?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.