Which versions of @baanx/abis are malicious?

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

How do I remediate @baanx/abis if I installed it?

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

I already installed @baanx/abis — how do I know if it already compromised me?

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

Yes — @baanx/abis is associated with the IN-MAL-2026-020263 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/abis 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/abis (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/abis across your stack and pipelines.

Malicious package

@baanx/abisnpm

@baanx/abis is a confirmed malicious npm package (MAL-2026-16351) 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/abis (npm)

MAL-2026-16351

Immediate action

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

npm uninstall @baanx/abis

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.

Malicious versions

1 flagged

9.9.11

Indicators of compromise (SHA-256)

647b64439f5d26821e6d749031b916e2ad3aa0cba8546488f8cc5e2fd263538b

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/abis (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/abis across your stack and pipelines.
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 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/abis 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/abis 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-020263

References

npmjs.com

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.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database