Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

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

Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.

osv · MAL-2026-14404

Published

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (0b7ff09078e56bd40b5ad38f72027a55a39067b82aaffb0bfe6891e3d6d912e8) 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. ## Source: ghsa-malware (a1ecad2acce84e767c2fa43fdafefcd276cfb48098a562f93707015c85ce40d4) 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
24 Aug 2026 12:31:45 UTC
Source modified
24 Aug 2026 17:00:14 UTC
Saved 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

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 10:12 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current