Malicious code in xzvbailey (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-16278
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (f961ec09baa139430fb2b04c3fef5350f16f659c8de585787a26f3c8535fca38) package.json declares the `libsignal` dependency as `github:tenka-san/libsignal-node`, a non-registry source pointing at a personal GitHub account with no tag or commit SHA. On `npm install`, npm fetches whatever the default branch's HEAD points to at that moment and runs any lifecycle scripts inside the cloned repo, so the owner of that account controls code that executes on the installer's machine. The account is unrelated to the upstream Baileys/libsignal publishers, and the package's own metadata is inconsistent (homepage and repository fields point at a Telegram URL while the bug tracker points at a different GitHub org, `pou-code/Baileys`), which is consistent with a repackaged Baileys lure rather than a legitimate fork.
- Source published
- 18 Sep 2026 02:57:47 UTC
- Source modified
- 18 Sep 2026 03:30:06 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.