Which versions of bcs-mini are malicious?

The following npm versions of bcs-mini are flagged malicious: 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate bcs-mini if I installed it?

bcs-mini 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 bcs-mini — how do I know if it already compromised me?

If bcs-mini was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is bcs-mini part of a known attack campaign?

Yes — bcs-mini is associated with the GHSA-9q3f-qc6p-62mm, IN-MAL-2026-017983, IN-MAL-2026-018096 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 bcs-mini across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bcs-mini (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bcs-mini across your stack and pipelines.

Malicious package

bcs-mininpm

bcs-mini is a confirmed malicious npm package (MAL-2026-14076) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bcs-mini (npm)

MAL-2026-14076

Immediate action

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

npm uninstall bcs-mini

What this malware does

bcs-mini presents itself as a BCS codec but contains an install/require-time payload in index.js that steals Sui wallet material. On module load, a self-invoked IIFE reads ~/.sui/sui.keystore, files under ~/.sui/sui_config/, and local.env* files matching SUI_/PK_B64/PRIVATE_KEY markers, base64-encodes their contents, and PUTs them to a hardcoded attacker-controlled GitHub repository via api.github.com/repos/<owner>/<repo>/contents/fingerprints/<ts>-<pid>.json. The destination host, owner, repo, and Bearer token are hidden as XOR-obfuscated character arrays reassembled at runtime using the key 'bcs-c0mpact-v10'. After exfiltration, the code overwrites index.js on disk to remove the /* compat-probe:start /... / compat-probe:end */ region so post-install inspection shows only a benign codec. A CI-environment check gates execution to reduce detection in build systems. The embedded GitHub Bearer token is the credential that authenticates the upload to the attacker's repository.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

2 flagged

1.0.01.0.1

Indicators of compromise (SHA-256)

2cabaabc178202b26609f4cd403279782d153548af197b164715fd8f795f41eb

90e476c27d0fcb2d394107a3fa8131c7b278152340ef508f1a13658e19cbbed5

a4da964d5f6af3f84c7ac1686ddc3069629de4aa40c6e15f57b63af536163858

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bcs-mini (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bcs-mini across your stack and pipelines.
If you installed it — respond
bcs-mini 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 bcs-mini was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks bcs-mini before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. bcs-mini on npm has been identified as a malicious package (versions 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-9q3f-qc6p-62mmIN-MAL-2026-017983IN-MAL-2026-018096

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bcs-mini-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