Which versions of @brick-v2/brand are malicious?

The following npm versions of @brick-v2/brand are flagged malicious: 999.0.1, 999.0.2, 999.0.3. Treat any of these as compromised.

How do I remediate @brick-v2/brand if I installed it?

@brick-v2/brand is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed @brick-v2/brand — how do I know if it already compromised me?

If @brick-v2/brand was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @brick-v2/brand part of a known attack campaign?

Yes — @brick-v2/brand is associated with the IN-MAL-2026-021313, IN-MAL-2026-021284, IN-MAL-2026-021300 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find @brick-v2/brand across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @brick-v2/brand (3 malicious versions).

Malicious package

@brick-v2/brandnpm

Advisory published Oct 9, 2026Updated Oct 12, 2026

@brick-v2/brand is a confirmed malicious npm package (MAL-2026-17714) that steals credentials and exfiltrates sensitive data (malicious versions 999.0.1, 999.0.2, 999.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

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

MAL-2026-17714

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall @brick-v2/brand

What this malware does

@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 {"src":"native","pkg":...,"h":...,"u":...,"os":...,"arch":...,"rel":...,"cwd":...,"e":{...}}, 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.

Malicious versions

3 flagged

999.0.1999.0.2999.0.3

Indicators of compromise (SHA-256)

197d8de60092ac86ecda23eedf003121f46b8a7c34c5f60eeabd6c23134e2983

a194395a620ef40055a22d7beccbab1e1ca0c662afe83b9ee2fb23d07ebaedc5

f7cfeebad59fc63be0a47be28ded37bfe722bbb39be81bb9d0fe9ba60f9db644

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @brick-v2/brand (3 malicious versions).
If you installed it — respond
@brick-v2/brand is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If @brick-v2/brand was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @brick-v2/brand on npm has been identified as a malicious package (versions 999.0.1, 999.0.2, 999.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021313IN-MAL-2026-021284IN-MAL-2026-021300

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @brick-v2/brand-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database