@baanx/blockchain-confignpm
Advisory published Updated
@baanx/blockchain-config is a confirmed malicious npm package (MAL-2026-16352) that steals credentials and exfiltrates sensitive data (malicious versions 9.9.9, 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in @baanx/blockchain-config (npm)
What this malware does
The package runs a bootstrap from both its install lifecycle script (node index.js) and its main module that invokes an obfuscated probe. The probe reads os.userInfo().username, os.hostname(), and the basename of process.cwd(), concatenates them with a static tag (bxcfg) and a timestamp, and performs a dns.resolve4 lookup against <tag>.<user>.<host>.<cwd>.<ts>.oob.algamil7x.xyz, exfiltrating installer identity over DNS to a non-first-party domain unrelated to the claimed baanx publisher. The exfil host and the os/dns/userInfo/hostname/cwd/resolve4 API references are hidden in String.fromCharCode/hex-decoded byte arrays in probe/impl.js and sibling files e9c3a6.js / f0d4b7.js, and the os and dns modules are loaded through module.constructor._load with decoded name arrays to defeat static analysis. Behavior fires automatically on npm install and on require('@baanx/blockchain-config').
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 @baanx/blockchain-config (2 malicious versions).
If you installed it — respond
@baanx/blockchain-config 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 @baanx/blockchain-config 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 @baanx/blockchain-config-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.