NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@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)

MAL-2026-10659
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @sauruslord/libsignal

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

1 flagged
2.0.2

Indicators of compromise (SHA-256)

cd9e1693f1fd1477895da39b9f225bbc2f7c4ee466044f9db234e0475e403849
b0c2cf2672d98396a7b66cb732741d269732f5faae72293ea46e06b879e7a45b

Detection & response playbook

Destructive / sabotage
  1. Find it

    Search your lockfiles and build artifacts for @sauruslord/libsignal (version 2.0.2).

  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.

  3. 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

No. @sauruslord/libsignal on npm has been identified as a malicious package (version 2.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-p9pv-49fq-8f6mIN-MAL-2026-010621

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.

Explore

@sauruslord/libsignal (npm) malicious package — MAL-2026-10659 | O3 Security