Malicious code in zero-baileys (npm)

--- _-= Per source details. Do not edit below this line.=-_ ## Source: amazon-inspector (58d472a4390be835fc8ffd5e62a7d3b2bb7270ad6ea651d9cd15bc7abd7735c8) package.json redirects the `libsignal` dependency to `npm:@otaxayun/libsignal-node@latest`. The `@latest` dist-tag is mutable and unpinned, so each `npm install` of zero-baileys resolves whatever tarball the `@otaxayun` scope currently publishes and executes any lifecycle scripts (preinstall/install/postinstall) it contains. Upstream Baileys resolves libsignal from a pinned source; the alias here substitutes an unofficial third-party scope as the trust root for a core cryptographic dependency, with no version pin and no integrity check. The static match on `child_process` + `https.request` + `POST` in lib/Utils/messages-media.js:28 corresponds to media-download helpers in the runtime library and is not itself an install-time exfil path. ## Source: ghsa-malware (e18ff0786d183c3327cf8291eac1d72b1fa8379e834e367c2341da1e87ab9e32) 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

18 Sep 2026 02:54:59 UTC

Source modified

19 Oct 2026 07:00:05 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.