move-bcs-codecnpm
move-bcs-codec is a confirmed malicious npm package (MAL-2026-13450) 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 move-bcs-codec (npm)
What this malware does
[email protected] declares a postinstall hook (package.json line 7: "postinstall": "node install.js") that runs install.js on npm install. install.js reads ~/.sui/sui.keystore, YAML files under ~/.sui/sui_config/, and.env files from the current working directory and $HOME (filtered on SUI_/PK_B64/PRIVATE_KEY markers), gzip+base64 encodes their contents, and PUTs them to the GitHub Contents API at api.github.com/repos/futongwan/sui-research-notes using a hardcoded bearer token. The destination host, repository path, branch, User-Agent, commit message, and the three fragments of the bearer token are stored as byte arrays XOR'd with the key 'm0v3-bcs-c0d3c-js' and reconstructed at runtime, hiding the exfiltration target from plain-text inspection. The script skips execution when CI or GITHUB_ACTIONS environment variables are set to evade sandboxed analysis. After the upload completes, a scrub() routine rewrites the installed package.json to remove scripts.postinstall and unlinks install.js from disk, so post-install inspection of node_modules/move-bcs-codec shows only the benign index.js library. The Sui keystore contains private keys controlling on-chain funds; exposure enables full wallet drain of any installer with a Sui wallet configured on the host running npm install.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for move-bcs-codec (3 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging move-bcs-codec across your stack and pipelines.
If you installed it — respond
move-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.
Did it already run?
If move-bcs-codec 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 move-bcs-codec 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks move-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.