GCVE-110-OSM-2026-11896

Package @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. ENTRY beacon.js (install-hook: node beacon.js postinstall) - Install Hook Executes Local JS File in package.json DESTINATION - 2 exfil (custom-c2) (values recorded in verified_iocs) EXFIL - Network Request in beacon.js: "https.get(" ADDITIONAL FINDINGS - Shell Command Execution in beacon.js: "child_process").exec" - Very New NPM Publisher Account - Rapid Version Publishing PAYLOAD FILES beacon.js