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

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

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

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

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

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

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

Malicious package

@brick-v2/iconsnpm

Advisory published Oct 9, 2026Updated Oct 12, 2026

@brick-v2/icons is a confirmed malicious npm package (MAL-2026-17717) 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/icons (npm)

MAL-2026-17717

Immediate action

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

npm uninstall @brick-v2/icons

What this malware does

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

@brick-v2/[email protected] is a dependency-confusion credential stealer. The package's package.json declares a preinstall script node index.js, and index.js's only behavior is to require a platform-specific prebuilt native addon from prebuilds/<platform>-<arch>/metrics.node. The native binary reads a curated list of CI and cloud secrets from the environment — AWS_SECRET_ACCESS_KEY, AWS_SESSION_TOKEN, GITHUB_TOKEN, NPM_TOKEN, NODE_AUTH_TOKEN, SYSTEM_ACCESSTOKEN, ACTIONS_RUNTIME_TOKEN, ACTIONS_ID_TOKEN_REQUEST_TOKEN, AZURE_DEVOPS_EXT_PAT, and similar — along with hostname, username, cwd, and OS fields, and POSTs them as JSON to the hardcoded attacker endpoint oob.s4yhii.com at path /native. The JS shim presents a benign Angular-style facade (forRoot, createLogger, version exports) under a plausible scoped name, while the real behavior lives in the opaque native binary; no build system, binding.gyp, or source is shipped. The inflated version 999.0.3 is designed to win semver resolution against any legitimate internal @brick-v2/icons package, targeting private registries via dependency confusion. Harm is auto-executed on npm install via the preinstall hook, before any user code runs.

Malicious versions

3 flagged

999.0.1999.0.2999.0.3

Indicators of compromise (SHA-256)

88a6c17d632b5a7940e2ea85e756778a9f39e80f8e91402e4b46f556b6bea317

915977ddb276c313e2977875d853dfba4eebd12f75ad0826008866b5059c68a8

ee63e57c42a765834eecfcad6263ffcd4daf526bd263d6ed2bc8401e9b1d4db2

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for @brick-v2/icons (3 malicious versions).
If you installed it — respond
@brick-v2/icons 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/icons 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/icons 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-021308IN-MAL-2026-021283IN-MAL-2026-021295

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

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