{"id":"MAL-2026-16062","revision":"b2f86d35fb004f2c9e9ebe7f025512bd","records":[{"revision":"b2f86d35fb004f2c9e9ebe7f025512bd","observedAt":"2026-10-24T13:17:17.793+00:00","statement":{"source":"osv","id":"MAL-2026-16062","aliases":[],"title":"Malicious code in @yongot/canary-mcp-test (npm)","description":"\n---\n_-= Per source details. Do not edit below this line.=-_\n\n## Source: amazon-inspector (b93b70d19f6065f9757e39a5d7f799ca9cfff26e2c47b6e4c51012a104885578)\nPackage @yongot/canary-mcp-test@2.0.0 ships beacon.js which runs `execSync('id')`, reads `os.hostname()`, and issues an HTTPS GET to a hardcoded webhook.site collector (https://webhook.site/b76376f8-118e-44f1-a5ee-8a73f55b137b) with stage, host, and id_output query parameters. The package.json postinstall hook invokes `node beacon.js postinstall`, so the beacon fires automatically on `npm install`. index.js (the package main) also requires beacon.js twice at load time, so any consumer that imports the package re-triggers the same exfiltration of the installer's Unix uid/gid/groups and hostname to the third-party webhook collector.\n","state":0,"publishedAt":"2026-09-09T01:40:56+00:00","modifiedAt":"2026-09-17T15:30:06.1752049+00:00","affected":[{"ecosystem":"npm","name":"@yongot/canary-mcp-test","ranges":[],"versions":["3.0.0","2.0.0","4.0.0","1.0.0"],"rawVersionEvidence":null}],"metrics":[],"references":["https://www.npmjs.com/package/@yongot/canary-mcp-test/v/3.0.0","https://www.npmjs.com/package/@yongot/canary-mcp-test/v/2.0.0","https://www.npmjs.com/package/@yongot/canary-mcp-test/v/4.0.0","https://www.npmjs.com/package/@yongot/canary-mcp-test/v/1.0.0"],"sourceUrl":"https://osv.dev/vulnerability/MAL-2026-16062","license":"OSV · upstream source license applies","key":"osv:MAL-2026-16062","identifiers":["MAL-2026-16062"]},"retained":false,"historicalAffected":[]}],"coverage":[]}