{"id":"MAL-2026-14135","revision":"f2d5214709d64985862ff5fae646d15e","records":[{"revision":"f2d5214709d64985862ff5fae646d15e","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-14135","aliases":[],"title":"Malicious code in @mohamed_nowisar/token3-check (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (10d463b1de43a90878da858dd595dadf43fcbbbb9d2e26cfd8b14ff6e0167457)\nThe package registers preinstall, install, and postinstall lifecycle hooks that all execute beacon.js. On any npm install, beacon.js collects the installer's hostname (os.hostname()), username (os.userInfo().username), current working directory (process.cwd()), platform/arch, Node.js version, and a curated set of CI-detection environment variables (including YANDEX_CI, GITHUB_ACTIONS, GITLAB_CI, JENKINS_URL) and POSTs them via https.request to a hardcoded endpoint at https://webhook.site/3687e44a-4e97-43c4-84c9-e6c93d4b2fbc. The package self-describes as a dependency-confusion canary targeting the Yandex build pipeline, but installers do not opt in to the beacon and the destination is a third-party inspection endpoint controlled by the publisher. Internal build-system identity and CI fingerprints leaked this way enable follow-on dependency-confusion attacks against the exposed pipelines.\n","state":0,"publishedAt":"2026-08-18T23:06:02+00:00","modifiedAt":"2026-08-18T23:15:11.5699779+00:00","affected":[{"ecosystem":"npm","name":"@mohamed_nowisar/token3-check","ranges":[],"versions":["0.0.1"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@mohamed_nowisar/token3-check/v/0.0.1"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-14135","license":"OSV · upstream source license applies","key":"osv:MAL-2026-14135","identifiers":["MAL-2026-14135"]},"retained":false,"historicalAffected":[]}],"coverage":[]}