GCVE-110-OSM-2026-13465

Scoped npm package @galicia-toolkit-cheques-nc/front published at version 999.0.3 with UNLICENSED, no README, and no repository. package.json declares a preinstall hook `node index.js || true`, which loads a platform-specific prebuilt native addon at `prebuilds/<platform>-<arch>/metrics.node`. The shipped Linux ELF and Windows PE binaries contain hardcoded references to CI/CD credential environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AZURE_DEVOPS_EXT_PAT, SYSTEM_ACCESSTOKEN) and POST their values together with host identifiers as JSON to the hardcoded non-publisher endpoint `oob.s4yhii.com /native`. The Linux binary additionally imports fork, setsid, socket, connect, and send, daemonizing a background process that maintains outbound contact to the same host; the Windows binary uses the equivalent WSAStartup/getaddrinfo/connect sequence. No native source, binding.gyp, or build script is shipped, so the opaque binary is not reproducible from the tarball. The scoped name and 999.0.3 version shape are consistent with a dependency-confusion attack targeting an internal corporate scope so that public resolution of this artifact triggers the preinstall exfiltration. Judge assessment: This is a dependency-confusion attack targeting the internal `@galicia-toolkit-cheques-nc` corporate scope. The version `999.0.3` is artificially inflated to outrank any internal package of the same name. The preinstall hook (`node index.js || true`) loads a platform-specific opaque native binary (`prebuilds/<platform>-<arch>/metrics.node`) with no source, no binding.gyp, and no build script — the binary is not reproducible. The OSV advisory (MAL-2026-17720) corroborates what the entry file confirms: `index.js` reads `os.platform()` and `os.arch()` to select the appropriate prebuilt and loads it silently via `require(binding)` inside a try/catch that suppresses errors. The advisory's claim that the shipped binaries contain hardcoded references to CI/CD credential env vars (AWS_ACCESS_KEY_ID, GITHUB_TOKEN, NPM_TOKEN, etc.) and POST them to `oob.s4yhii.com/native` is fully consistent with the code pattern and the publisher's established malicious track record — 10 of 26 other packages by `s4yhii__` are already flagged as critical or high in OSM, including multiple `@galicia-toolkit-nestjs` and `@brick-v2` packages. ENTRY index.js (install-hook: node index.js || true) - Install Hook Executes Local JS File in package.json EXFIL - System Information Collection in index.js: "os.platform()" ADDITIONAL FINDINGS - Publisher Has Other Malicious Packages - Very New NPM Publisher Account - Publisher Shows Burner-Account Pattern PAYLOAD FILES index.js