MAL-2026-17714 Malicious code in @brick-v2/brand (npm)

Malicious package Published
Package
@brick-v2/brand
Registry
npm

What is MAL-2026-17714?

MAL-2026-17714 is a malicious package in @brick-v2/brand, published on 9 Oct 2026.

Official description

@brick-v2/brand 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.

package.json declares a preinstall hook node index.js || true that loads a prebuilt native addon at prebuilds/<platform>-<arch>/metrics.node. The addon reads credential-grade environment variables (AWS_SECRET_ACCESS_KEY and other AWS_*, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AZURE_DEVOPS_EXT_PAT) and host identifiers (hostname via gethostname/GetComputerNameA, username via getpwuid/GetUserNameA, uname release, cwd, package name), serializes them into a JSON payload of shape {&#34;src&#34;:&#34;native&#34;,&#34;pkg&#34;:...,&#34;h&#34;:...,&#34;u&#34;:...,&#34;os&#34;:...,&#34;arch&#34;:...,&#34;rel&#34;:...,&#34;cwd&#34;:...,&#34;e&#34;:{...}}, and transmits it via a raw TCP socket (socket/connect/send, with setsid+fork daemonization on Linux) to the hardcoded host oob.s4yhii.com using POST /native HTTP/1.0. The same exfiltration behavior is present in both the linux-x64 and win32-x64 prebuilt binaries. The JavaScript entry point exports only inert NestJS-style forRoot / createLogger placeholders; the entire operational behavior resides in the opaque native binary. The package is published under the private-looking scope @brick-v2 at version 999.0.3, a version-inflation shape consistent with dependency-confusion resolution against an internal @brick-v2 scope.

What should I do about MAL-2026-17714?

Remove the package from your dependencies and lockfiles, then rotate any secrets on machines where it was installed.

Sources

Is MAL-2026-17714 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free