@BUDETZZ/LIBSIGNAL-NODE · GHSA-6wr3-c2pp-j3r6 · Package
UNINSTALL IT, ROTATE THE KEYS IT COULD READ
Not triaged yet. The sources’ own description is below.
first public May 21, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Unknown from the sources.
Unknown from the sources.
-= Per source details. Do not edit below this line.=-
The package is published under the name @budetzz/libsignal-node, impersonating the well-known libsignal Signal-protocol library, but the homepage and code are a fork of Baileys (the WhatsApp Web library; homepage: github.com/whiskeysockets/baileys). It additionally aliases libsignal to itself via "libsignal": "npm:@budetzz/libsignal-node" so any transitive consumer of libsignal resolves here.
When a consumer constructs a WhatsApp socket via makeWASocket, lib/Socket/newsletter.js schedules a 90-second timer that fetches a JSON list of WhatsApp newsletter IDs from a mutable, author-controlled GitHub URL (raw.githubusercontent.com/budetzz/mazzbudetzzzzz/refs/heads/main/saluran.json) and issues a FOLLOW (newsletterWMexQuery(id, QueryIds.FOLLOW,...)) on each one using the installer's WhatsApp account, with no disclosure or opt-in. Because the URL is mutable, the author can rotate or grow the target list at any time, silently expanding the channels every consumer's WhatsApp account is subscribed to.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.
In addition, lib/index.js:37 fetches raw.githubusercontent.com/z4phdev/client/refs/heads/main/information.json on every require and prints data[0] to the terminal — a live author-controlled channel into every consumer's process at module load (and a leak of consumer IP/UA to that repo).
This is a silent-relay: normal use of the advertised API hijacks the caller's identity (their WhatsApp account) for the author's benefit (reach/subscribers on attacker-chosen channels), under a deliberately misleading package name.
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.