Malicious code in @dgxeon13/libsignal-node (npm)
Exploitation and risk
Source statusCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
Which CVEs have scores here?
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.
osv · MAL-2026-13929
Publishednpm/@dgxeon13/libsignal-node impersonates Signal's libsignal Node binding. On require of index.js, after a short delay it runs install.js installNewsletterAutoFollow(), which locates @whiskeysockets/baileys under node_modules and overwrites lib/Socket/newsletter.js with an embedded payload that performs remote-controlled consentless WhatsApp newsletter auto-follow (fetch DGXeon13/strings after 120s, silent FOLLOW). This is supply-chain tampering of a third-party package at import time. Distinct from the separately reported @dgxeon/libsignal-node (different npm scope). Used as the libsignal alias from @dreamguyxeon/baileyx. Related campaign OSV: MAL-2026-2252, MAL-2025-806. Tarball sha256: 46e4b9fd62489e1e28c88f8ebac77cf0fa6c48639cd6d548bdb097ca6793d157.
- Source published
- 10 Aug 2026 22:30:00 UTC
- Source modified
- 13 Aug 2026 06:30:10 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.