Which versions of ts-bn-proto are malicious?

The following npm versions of ts-bn-proto are flagged malicious: 5.8.1. Treat any of these as compromised.

How do I remediate ts-bn-proto if I installed it?

ts-bn-proto 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 ts-bn-proto — how do I know if it already compromised me?

If ts-bn-proto 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 ts-bn-proto part of a known attack campaign?

Yes — ts-bn-proto is associated with the IN-MAL-2026-009187, GHSA-wxpc-r4jx-9jrw 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 ts-bn-proto 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 ts-bn-proto (version 5.8.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging ts-bn-proto across your stack and pipelines.

Malicious package

ts-bn-protonpm

ts-bn-proto is a confirmed malicious npm package (MAL-2026-6695) that steals credentials and exfiltrates sensitive data (malicious version 5.8.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ts-bn-proto (npm)

MAL-2026-6695

Immediate action

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

npm uninstall ts-bn-proto

What this malware does

Malicious npm package published as part of a coordinated DeFi-themed infostealer campaign. ts-bn-proto embeds an infostealer payload directly in index.js with a base64-encoded C2 address (data-stream.space), executed at install time via a postinstall hook. The payload harvests cryptocurrency wallet vaults (MetaMask, Phantom, Solflare, OKX, Coinbase, TrustWallet, Backpack, TronLink), browser cookies and credentials, SSH keys, AWS credentials, developer secrets, and password manager databases, then exfiltrates all data to the attacker-controlled C2.

The package's index.js requires Node's child_process module and contains execSync calls that spawn bash and zsh (around lines 301 and 317). Without further trace evidence, the intent and reachability of these shell invocations cannot be confirmed — they may be benign tooling or a path to executing arbitrary commands on the installer's machine. Given the presence of shell execution primitives in the main module, manual review of index.js around the cited lines is warranted before allowing this package into a build environment.

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

1 flagged

5.8.1

Indicators of compromise (SHA-256)

815835f44f5257a8dda47ca05ec01f05d4f4ead35850358445a644639ab00dd5

5a54a40adf51915413224d33240db940faf72bdc1efe4bde20be872278e5ebaf

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

Campaign

IN-MAL-2026-009187GHSA-wxpc-r4jx-9jrw

References

Credits

Amazon Inspector · finder
SafeDep · finder

Detect & block this

O3 blocks ts-bn-proto-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