{"id":"MAL-2026-16279","revision":"e8fed7fe36cb4982b47f6be1db50deca","records":[{"revision":"e8fed7fe36cb4982b47f6be1db50deca","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-16279","aliases":[],"title":"Malicious code in xzvbailsx (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (ac9176da252791a96b93c24e702c2245fb96d9655cdf9f31d61e9bc3e0c21528)\npackage.json declares the dependency `libsignal` with source `github:tenka-san/libsignal-node`, an unpinned GitHub ref with no commit SHA, tag, or integrity hash. On `npm install`, npm fetches whatever HEAD of that repository currently points at and executes any lifecycle scripts (preinstall/install/postinstall) it contains on the installer's machine. The referenced GitHub account is a personal repository unrelated to the WhiskeySockets/Baileys upstream that this package forks. Provenance is further obscured by an identity mismatch: the package is published as `xzvbailsx` but README/examples describe it as `@XzV-RxVz/xbails`, and the `repository` field points to Telegram handles (`t.me/JustRxVz`, `t.me/XzV_ExpzC`) rather than a source repository.\n","state":0,"publishedAt":"2026-09-18T02:57:57+00:00","modifiedAt":"2026-09-18T03:30:06.0567603+00:00","affected":[{"ecosystem":"npm","name":"xzvbailsx","ranges":[],"versions":["1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/xzvbailsx/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-16279","license":"OSV · upstream source license applies","key":"osv:MAL-2026-16279","identifiers":["MAL-2026-16279"]},"retained":false,"historicalAffected":[]}],"coverage":[]}