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

@dreamguyxeon/libsignal-nodenpm

@dreamguyxeon/libsignal-node is a confirmed malicious npm package (MAL-2026-13931) that executes malicious code on install (malicious version 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

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

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

What this malware does

npm/@dreamguyxeon/libsignal-node has the same import-time supply-chain tampering as @dgxeon13/[email protected]: on require it patches @whiskeysockets/baileys lib/Socket/newsletter.js with remote-controlled consentless WhatsApp newsletter auto-follow code (fetch DGXeon13/strings after 120s, silent FOLLOW). Used as the libsignal npm alias dependency from [email protected]. Related campaign OSV: MAL-2026-2252, MAL-2025-806. Tarball sha256: 41906336d7a9cbf416ca8ac3e01af4ffad13a1048cd306390734fa18a061ba8c.

Malicious versions

1 flagged
1.0.1

Detection & response playbook

Malicious package

  1. Find it

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

  2. If you installed it — respond

    Remove @dreamguyxeon/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 @dreamguyxeon/libsignal-node 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.

  4. How O3 protects you

    O3 blocks @dreamguyxeon/libsignal-node 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. @dreamguyxeon/libsignal-node on npm has been identified as a malicious package (version 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

  • pkgwarden · finder

Detect & block this

O3 blocks @dreamguyxeon/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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database
@dreamguyxeon/libsignal-node (npm) malicious package — MAL-2026-13931 | O3 Security