What does the @baanx/blockchain-config malware do?

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 ` . . . . .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.

Which versions of @baanx/blockchain-config are malicious?

The following npm versions of @baanx/blockchain-config are flagged malicious: 9.9.11. Treat any of these as compromised.

How do I remediate @baanx/blockchain-config if I installed it?

@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.

I already installed @baanx/blockchain-config — how do I know if it already compromised me?

If @baanx/blockchain-config 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 @baanx/blockchain-config part of a known attack campaign?

Yes — @baanx/blockchain-config is associated with the IN-MAL-2026-020264 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 @baanx/blockchain-config 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 @baanx/blockchain-config (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @baanx/blockchain-config across your stack and pipelines.

Malicious package

@baanx/blockchain-confignpm

@baanx/blockchain-config is a confirmed malicious npm package (MAL-2026-16352) that steals credentials and exfiltrates sensitive data (malicious version 9.9.11). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @baanx/blockchain-config (npm)

MAL-2026-16352

Immediate action

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

npm uninstall @baanx/blockchain-config

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').

Malicious versions

1 flagged

9.9.11

Indicators of compromise (SHA-256)

0b6dec4d715e2863e7f55749d6d2a390926f3f2f1df62e4de223c6acc818632d

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 @baanx/blockchain-config (version 9.9.11). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @baanx/blockchain-config across your stack and pipelines.
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 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 @baanx/blockchain-config 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. @baanx/blockchain-config on npm has been identified as a malicious package (version 9.9.11 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-020264

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database