NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

sui-bcs-codecnpm

Advisory published Updated

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

Malicious code in sui-bcs-codec (npm)

MAL-2026-13767
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall sui-bcs-codec

What this malware does

On require('sui-bcs-codec'), a hidden IIFE labeled 'compat-probe' in index.js reads ~/.sui/sui.keystore, ~/.sui/sui_config/.yaml, and.env files under cwd and $HOME matching SUI_/PK_B64/PRIVATE_KEY markers, gzip+base64-encodes them, and PUTs the bundle via https.request to api.github.com. The destination host, repo path (futongwan/sui-research-notes), User-Agent, and a GitHub Bearer token are stored as byte arrays XOR-encoded with the key 'sui-bcs-c0d3c-v9' and reconstructed at runtime. After the upload runs, index.js rewrites itself via fs.writeFileSync(__filename,...) to remove the payload block. Sui keystore files hold private keys controlling on-chain wallets, so any installer of this package suffers immediate wallet-key theft on the first import. The Bearer token embedded in the package is the attacker's write credential for the receiving GitHub repo.

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

3 flagged
1.0.01.0.11.0.2

Indicators of compromise (SHA-256)

769156a44eb0f6216b2f5a42e637162c06936da99b7c0d7ea720cec2e50d8203
11a215fced265f75473130d499c7d6ea6097f63aa19c595fc5445a56633b1c6e
3ac7851fd466abbc35844a98c88a8fe2b9d4c1de79dc0dea23a18dd188483221
aeae51d5ddc557b635d06075b8707f90cef6ac011aae85324a54c570f64fe2f3

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for sui-bcs-codec (3 malicious versions).

  2. If you installed it — respond

    sui-bcs-codec 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.

  3. Did it already run?

    If sui-bcs-codec 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. sui-bcs-codec on npm has been identified as a malicious package (versions 1.0.0, 1.0.1, 1.0.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-2wqc-3243-4hxmIN-MAL-2026-017431IN-MAL-2026-017432IN-MAL-2026-017462

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks sui-bcs-codec-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

sui-bcs-codec (npm) malicious package — MAL-2026-13767 | O3 Security