{"id":"MAL-2026-16387","revision":"4f90a5ba7cf145c883a0a64264ee7730","records":[{"revision":"4f90a5ba7cf145c883a0a64264ee7730","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-16387","aliases":[],"title":"Malicious code in @mr-supun-fernando/supunmd-bail (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (86c68c82f6ead4ab3b823b81fd6805991bfdd65cdc901d83aeb561cdd8f27b19)\npackage.json declares `\"libsignal\": \"github:tenka-san/libsignal-node\"` — an off-registry dependency source pointing at a personal-user GitHub repository with no commit SHA, no tag, and no integrity check. On `npm install`, npm clones the current tip of that repository and installs whatever it contains, running any lifecycle scripts (`preinstall`/`install`/`postinstall`/`prepare`) inside the fetched tree on the installer's machine. The dependency key `libsignal` shadows the well-known Signal protocol library, but the source is a personal user's fork rather than the upstream signalapp organization, so whoever controls the tenka-san/libsignal-node repository controls install-time code execution on every installer of this package. The source is mutable — content that resolves benign today can be replaced without any change to this package. A secondary observation: lib/Utils/generics.js line 403 references `ping`, but this is unrelated to the primary install-time execution concern.\n","state":0,"publishedAt":"2026-09-22T16:05:01+00:00","modifiedAt":"2026-09-22T16:30:07.5611715+00:00","affected":[{"ecosystem":"npm","name":"@mr-supun-fernando/supunmd-bail","ranges":[],"versions":["3.0.3"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@mr-supun-fernando/supunmd-bail/v/3.0.3"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-16387","license":"OSV · upstream source license applies","key":"osv:MAL-2026-16387","identifiers":["MAL-2026-16387"]},"retained":false,"historicalAffected":[]}],"coverage":[]}