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

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

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

@brick-v2/core 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/core — how do I know if it already compromised me?

If @brick-v2/core 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/core part of a known attack campaign?

Yes — @brick-v2/core is associated with the IN-MAL-2026-021309, IN-MAL-2026-021315 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/core across my projects, lockfiles, and CI pipelines?

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

Malicious package

@brick-v2/corenpm

Advisory published Oct 9, 2026Updated Oct 12, 2026

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

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

MAL-2026-17715

Immediate action

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

npm uninstall @brick-v2/core

What this malware does

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

The package's main entry index.js loads a prebuilt native binary at prebuilds/<platform>-<arch>/metrics.node inside a top-level try/catch, executing native code within the Node process as soon as the module is required. The ELF binary reads credential-grade environment variables including AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, and ACTIONS_ID_TOKEN_REQUEST_TOKEN, along with hostname, uid, and current working directory, and POSTs them as JSON to the hardcoded host oob.s4yhii.com via a raw socket (POST /native HTTP/1.0). The native code also invokes fork/setsid to detach from the parent process. The package is published as @brick-v2/core at version 999.0.1 with a trivial JS wrapper, a generic core module description, and UNLICENSED — a shape consistent with a dependency-confusion payload targeting a private @brick-v2 scope so that npm resolution prefers this public version over an internal package.

Malicious versions

2 flagged

999.0.1999.0.2

Indicators of compromise (SHA-256)

13cc187815f5f1b0024df22bab31f1735b2bb864854af665422a8401a7672226

90c1fd9505ce4256620f9cb647e3a57a5af52539aa1e717a3eecb0485dec8c83

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @brick-v2/core (2 malicious versions).
If you installed it — respond
@brick-v2/core 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/core 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/core on npm has been identified as a malicious package (versions 999.0.1, 999.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-021309IN-MAL-2026-021315

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks @brick-v2/core-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