@baanx/abisnpm
Advisory published Updated
@baanx/abis is a confirmed malicious npm package (MAL-2026-16351) 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/abis (npm)
What this malware does
Package declares scripts.install: node index.js, which loads runtime/support/telemetry/probe/impl.js. That module reads the installer's OS username (os.userInfo().username), hostname (os.hostname()), and current working directory basename (process.cwd()), joins them with a timestamp and the prefix bxabis under the suffix oob.algamil7x.xyz, and issues a dns.resolve4 lookup on the composed name — a DNS-tunnel exfiltration of installer host identity to an attacker-controlled domain. The behavior fires automatically on npm install and again on require. The module names, method references (_load('os'), _load('dns'), userInfo, hostname, cwd, resolve4), the prefix bxabis, and the destination domain are all reconstructed from char-code hex arrays, and the surrounding files carry telemetry/connectivity probe cover-story comments. The destination is unrelated to any legitimate endpoint of a smart-contract ABI library.
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/abis (2 malicious versions).
If you installed it — respond
@baanx/abis 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/abis 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/abis-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.