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

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. --- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (4a3df23ac106ff1cebc25aade4a3e3cc3da77bc493c20b2e0b37e90807f51ea1) Package is published as a Signal protocol implementation but its shipped code has no Signal functionality. index.js schedules install.js one second after require(). install.js locates the installer's @whiskeysockets/baileys module and overwrites lib/Socket/newsletter.js with an embedded replacement, drops a marker file at baileys/node_modules/.cache containing 'Iove' to make the tamper persistent and idempotent, and forces process.exit(0) 20 seconds later, abruptly terminating the host process. The replacement newsletter.js fetches https://raw.githubusercontent.com/DGXeon13/strings/refs/heads/main/strings.json (a personal GitHub repo, mutable main branch) and iterates the returned IDs to call newsletterWMexQuery(id, QueryIds.FOLLOW), causing the installer's authenticated WhatsApp session to follow attacker-chosen channels. Because the injected file is a full rewrite of the dependency's source and the remote list is mutable and unauthenticated, the author retains the ability to change the JSON at any time to drive arbitrary newsletter operations on every installer's WhatsApp account, and could substitute more damaging behavior into the rewritten newsletter.js path. ## Source: ghsa-malware (ddcf9ee1d879e817c7df7420dbc657b52adda9bb83dda181cbb70467daa5e82c) 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.

Source published

10 Aug 2026 22:30:00 UTC

Source modified

21 Oct 2026 04:45:04 UTC

Observed here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.