cbc97b7anpm
Advisory published Updated
cbc97b7a is a confirmed malicious npm package (MAL-2026-15878) that steals credentials and exfiltrates sensitive data (malicious versions 1.1787999566.0, 1.1787999998.0, 1.1788000497.0…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in cbc97b7a (npm)
What this malware does
The tarball ships only package.json with no code, scripts, main, or bin. The description field contains a ~41KB base64-encoded POSIX shell script that, when decoded and executed, downloads an xmrig cryptominer from gitlab.com/albertotrindade131/al and a github.com/lucas77335/xmrig-amd mirror, installs cron-based persistence, and mines Monero to the hardcoded pool xmr.kryptex.network:8029 with an embedded wallet/worker identifier. Operational strings (pool host, wallet, miner URLs, fallback bare-IP C2 hosts 66.23.199.44, 45.94.31.89, 139.59.59.33, 154.89.152.115, 84.21.173.223, 142.132.131.238) are individually base64-encoded and decoded at runtime via a helper function. The payload script self-references https://registry.npmjs.org/cbc97b7a/latest, indicating the package is designed to be pulled by a companion loader that fetches this metadata and pipes the decoded description to sh, delivering miner installation, persistence, and secondary C2 fetches to the installer.
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
Search your lockfiles and build artifacts for cbc97b7a (6 malicious versions).
If you installed it — respond
cbc97b7a 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 cbc97b7a 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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks cbc97b7a-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.