Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

@blurrydespair/libsignal-nodenpm

Advisory published Updated

@blurrydespair/libsignal-node is a confirmed malicious npm package (MAL-2026-14404) that executes malicious code on install (malicious versions 2.2.7, 2.2.9). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @blurrydespair/libsignal-node (npm)

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

What this malware does

Package advertises itself as 'Open Whisper Systems libsignal for Node.js' but ships an install.js that has nothing to do with libsignal. On require() of the package, index.js schedules install.installNewsletterAutoFollow() via setTimeout; that function locates @whiskeysockets/baileys inside the installer's node_modules and overwrites lib/Socket/newsletter.js with a hardcoded modified copy, then process.exit(0)s. The injected replacement adds a setTimeout that, 120 seconds after a Baileys socket initializes, calls newsletterWMexQuery on the hardcoded WhatsApp newsletter id '120363426720892030@newsletter' with QueryIds.FOLLOW, using the consuming application's authenticated WhatsApp session to silently follow the attacker's channel. Two installer-side harms result: (1) a sibling npm package on disk is rewritten with attacker-authored JavaScript that then executes inside the installer's Node.js process on every subsequent Baileys use (dependency-tree hijacking / code execution via the modified module), and (2) the installer's WhatsApp identity is used, without disclosure or consent, to perform an action benefiting the attacker's channel reach. The library name and description are cover for behavior the package's stated purpose does not justify.

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

2 flagged
2.2.72.2.9

Indicators of compromise (SHA-256)

a1ecad2acce84e767c2fa43fdafefcd276cfb48098a562f93707015c85ce40d4
0b7ff09078e56bd40b5ad38f72027a55a39067b82aaffb0bfe6891e3d6d912e8
e04a0610915859dad181cfaa4940f0a1feac4dc0e7d152282d168272e123b5f6

Detection & response playbook

Malicious package
  1. Find it

    Search your lockfiles and build artifacts for @blurrydespair/libsignal-node (2 malicious versions).

  2. If you installed it — respond

    Remove @blurrydespair/libsignal-node from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

  3. Did it already run?

    If @blurrydespair/libsignal-node 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. @blurrydespair/libsignal-node on npm has been identified as a malicious package (versions 2.2.7, 2.2.9 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-rw8r-gxqp-rwfhIN-MAL-2026-018623IN-MAL-2026-018624

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @blurrydespair/libsignal-node-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

@blurrydespair/libsignal-node (npm) malicious package — MAL-2026-14404 | O3 Security