GCVE-110-OSM-2026-13453

@brick-v2/icons@999.0.3 is a dependency-confusion credential stealer. The package's package.json declares a preinstall script `node index.js`, and index.js's only behavior is to require a platform-specific prebuilt native addon from `prebuilds/<platform>-<arch>/metrics.node`. The native binary reads a curated list of CI and cloud secrets from the environment — AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AZURE_DEVOPS_EXT_PAT, and similar — along with hostname, username, cwd, and OS fields, and POSTs them as JSON to the hardcoded attacker endpoint `oob.s4yhii.com` at path `/native`. The JS shim presents a benign Angular-style facade (`forRoot`, `createLogger`, `version` exports) under a plausible scoped name, while the real behavior lives in the opaque native binary; no build system, binding.gyp, or source is shipped. The inflated version `999.0.3` is designed to win semver resolution against any legitimate internal `@brick-v2/icons` package, targeting private registries via dependency confusion. Harm is auto-executed on `npm install` via the preinstall hook, before any user code runs. Judge assessment: This is a dependency-confusion credential stealer. The package uses an inflated version (999.0.3) to win semver resolution against a legitimate internal @brick-v2/icons package, and its preinstall hook (`node index.js || true`) executes immediately on npm install. The index.js constructs a path to a platform-specific native binary at `prebuilds/<os.platform()>-<os.arch()>/metrics.node` and requires it — the JS facade (forRoot, createLogger) is purely cosmetic cover. Per the OSV advisory (MAL-2026-17717), the native binary exfiltrates CI/cloud secrets (AWS_SECRET_ACCESS_KEY, GITHUB_TOKEN, NPM_TOKEN, AZURE_DEVOPS_EXT_PAT, etc.) along with hostname/username/cwd to a hardcoded attacker endpoint `oob.s4yhii.com/native`. The publisher `s4yhii__` is a brand-new burner account with 5 other packages already flagged as malicious in OSM, including a critical-severity package (@s4yhiitestpoc/r3-https), confirming a pattern of adversarial publishing. 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