{"id":"MAL-2026-16389","revision":"73428f38e7654a3183d5ad0ddee9117e","records":[{"revision":"73428f38e7654a3183d5ad0ddee9117e","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-16389","aliases":[],"title":"Malicious code in noverojava (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (a7fbf0d1519b05868b34e9e2c1d3588a0596003a5cb53e4cd28fd3a856ecff26)\npackage.json declares the runtime dependency `libsignal` as `github:tenka-san/libsignal-node` rather than a registry version range or pinned commit SHA. On `npm install`, npm fetches the current HEAD of that fork's default branch and executes any lifecycle scripts it defines. The fork is under a third-party GitHub account (not the upstream WhiskeySockets libsignal-node maintainer), has no commit pin, and no integrity check, so whoever controls that account controls code that runs on the installer's machine at install time. The package presents as a Baileys/WhatsApp library fork; the static match on lib/Utils/generics.js line 403 (ping/GET tokens) is consistent with normal Baileys network code and is not independently indicative of exfiltration.\n","state":0,"publishedAt":"2026-09-22T18:07:09+00:00","modifiedAt":"2026-09-22T18:45:05.9578483+00:00","affected":[{"ecosystem":"npm","name":"noverojava","ranges":[],"versions":["1.1.0","1.0.9"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/noverojava/v/1.1.0","https://www.npmjs.com/package/noverojava/v/1.0.9"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-16389","license":"OSV · upstream source license applies","key":"osv:MAL-2026-16389","identifiers":["MAL-2026-16389"]},"retained":false,"historicalAffected":[]}],"coverage":[]}