Which versions of @sauruslord/libsignal are malicious?

The following npm versions of @sauruslord/libsignal are flagged malicious: 2.0.2. Treat any of these as compromised.

How do I remediate @sauruslord/libsignal if I installed it?

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

I already installed @sauruslord/libsignal — how do I know if it already compromised me?

If @sauruslord/libsignal was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is @sauruslord/libsignal part of a known attack campaign?

Yes — @sauruslord/libsignal is associated with the GHSA-p9pv-49fq-8f6m, IN-MAL-2026-010621 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @sauruslord/libsignal across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sauruslord/libsignal (version 2.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sauruslord/libsignal across your stack and pipelines.

Malicious package

@sauruslord/libsignalnpm

@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

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for @sauruslord/libsignal (version 2.0.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @sauruslord/libsignal across your stack and pipelines.
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 ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks @sauruslord/libsignal before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database