MAL-2026-17691 Malicious code in @galicia-toolkit/tag-manager (npm)

@galicia-toolkit/tag-manager claims the @galicia-toolkit scope and describes itself as a dependency-confusion PoC. Its postinstall hook runs node postinstall.js || true on npm install; the script collects host, platform, runtime, network, and environment data, then sends it over HTTP to oob.s4yhii.com:9999 and encodes hostname, username, platform, and architecture in DNS queries to subdomains of oob.s4yhii.com. The npm account s4yhii_ published versions 999.0.3 and 999.0.5 on 2026-10-08; 999.0.6 runs the same node postinstall.js || true command on install, sends the same DNS queries, and connects to 66.94.100.203:9999.

@galicia-toolkit/[email protected] is a scoped dependency-confusion squat whose entire payload runs from a postinstall hook. On npm install, postinstall.js reads a curated list of credential-grade environment variables (AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN), enumerates the full process.env key list, and collects host reconnaissance (hostname, username, platform, arch, kernel, cwd, uid, external IPs, CPU/memory). The collected data is exfiltrated over two channels to a hardcoded external host: an HTTP POST to oob.s4yhii.com:9999/dep-confusion, and DNS beacons encoding hostname/username under *.dc.oob.s4yhii.com. index.js is empty — the package has no library functionality; its only effect is the install-time exfiltration. The package.json uses an inflated 999.0.6 version consistent with winning resolution against an internal @galicia-toolkit scope. A self-label as a bug-bounty PoC in the description does not change the behavior: any installer that resolves this scoped name has its cloud and CI credentials sent to a non-first-party host.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.