@sauruslord/libsignalnpm
Advisory published Updated
@sauruslord/libsignal is a confirmed malicious npm package (MAL-2026-10659) that runs destructive / sabotage code (malicious version 2.0.2). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @sauruslord/libsignal (npm)
What this malware does
Package name impersonates Open Whisper Systems' libsignal-node but ships unrelated code. On require() of index.js, after a 1-second delay, install.js locates the installer's @whiskeysockets/baileys directory and overwrites lib/Socket/newsletter.js with an attacker-supplied stub. The replacement stub schedules a setTimeout that, 120 seconds after the host application starts, silently invokes newsletterWMexQuery('120363425694844039@newsletter', QueryIds.FOLLOW) using the installer's authenticated WhatsApp session — auto-following an attacker-controlled WhatsApp newsletter channel without user consent. The original newsletter.js is destroyed (a restoreBackup export is referenced but no backup is ever written). install.js also schedules process.exit(0) 20 seconds after import, terminating the host application. Declared dependencies list crypto, fs, and path as npm packages rather than Node builtins, pulling in registry placeholders/typosquats. Installer harm: any developer who imports this package and also depends on @whiskeysockets/baileys has a third-party dependency silently rewritten on disk and their authenticated WhatsApp session abused on every subsequent run.
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.
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Destructive / sabotageFind it
Search your lockfiles and build artifacts for @sauruslord/libsignal (version 2.0.2).
If you installed it — respond
@sauruslord/libsignal carries a destructive/sabotage payload. Remove it immediately, restore any affected data from clean backups, and verify integrity of build outputs that may have been tampered with.
Did it already run?
If @sauruslord/libsignal was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.
Frequently asked questions
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks @sauruslord/libsignal-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.