MAL-2026-17720 Malicious code in @galicia-toolkit-cheques-nc/front (npm)
- Package
- @galicia-toolkit-cheques-nc/front
- Registry
- npm
What is MAL-2026-17720?
MAL-2026-17720 is a malicious package in @galicia-toolkit-cheques-nc/front, published on 9 Oct 2026.
Official description
@galicia-toolkit-cheques-nc/front is a dependency confusion package published to npm on 2026-10-09 by the account s4yhii__, targeting the internal @galicia-toolkit-* / @brick-v2 package namespaces with inflated versions (e.g. 999.0.x). Early versions resolve <hostname>.<tag>.dc.oob.s4yhii.com via DNS to beacon the victim's hostname. Later versions run node index.js from a preinstall hook, which loads a bundled native addon (prebuilds/<platform>-<arch>/metrics.node, Linux and Windows builds). The addon forks a detached process that collects hostname, username, OS/arch, cwd and the full values of CI/cloud secrets from environment variables (NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, SYSTEM_ACCESSTOKEN, AZURE_DEVOPS_EXT_PAT and others) and sends them as JSON via HTTP POST /native to oob.s4yhii.com:9999.
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.
What should I do about MAL-2026-17720?
Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.