Malicious code in @akapaki/baileys (npm)
Collected exploitation and prediction evidence
Risk source coverageCISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
osv · MAL-2026-17285
Published--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (c14fdf44df68d2544cc235039ef40a99c7df7bcbfc968e8d5809762031f0dd16) @akapaki/[email protected] is an unofficial republish of the Baileys WhatsApp library under a new scope (author `paki`, empty README, repository `pernapasquale647-dotcom/paki-baileys`). Its package.json declares the `libsignal` dependency as `github:pernapasquale647-dotcom/paki-libsignal` — a personal GitHub source with no commit SHA, tag, or integrity pin. `npm install` will fetch whatever the repo's default branch currently contains and run any lifecycle scripts inside it on the installer's machine, giving the repository owner unilateral, unaudited control over code executed at install time. The shipped lib/ has not been diffed against upstream Baileys, so behavioral drift from the legitimate library cannot be excluded. ## Source: ghsa-malware (05141dbb72ff164991b09e418665ce4b79680d12dee2eccfd7b7655705529569) 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
- 29 Sep 2026 21:11:58 UTC
- Source modified
- 8 Oct 2026 13: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.