Which versions of bitcoinjs-wallet are malicious?

The following npm versions of bitcoinjs-wallet are flagged malicious: 5.4.2. Treat any of these as compromised.

How do I remediate bitcoinjs-wallet if I installed it?

bitcoinjs-wallet 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 bitcoinjs-wallet — how do I know if it already compromised me?

If bitcoinjs-wallet 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 bitcoinjs-wallet part of a known attack campaign?

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

Malicious package

bitcoinjs-walletnpm

bitcoinjs-wallet is a confirmed malicious npm package (MAL-2026-13258) that steals credentials and exfiltrates sensitive data (malicious version 5.4.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bitcoinjs-wallet (npm)

MAL-2026-13258

Immediate action

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

npm uninstall bitcoinjs-wallet

What this malware does

[email protected] is a typosquat of bitcoinjs-lib that performs credential theft at module load. On require(), index.js collects hostname, username, homedir, platform, cwd and the entire process.env, JSON-stringifies and base64-encodes the payload, and transmits it via an HTTPS GET to the Telegram Bot API using a hardcoded bot token and chat_id 8969499041. A marker file in the OS tmpdir suppresses repeat sends. The bulk process.env dump captures any credentials the installer has in the environment (AWS_*, NPM_TOKEN, GITHUB_TOKEN, CI secrets, wallet-related variables). The package advertises itself as a 'Drop-in replacement for bitcoinjs-lib': if bitcoinjs-lib is present it is re-exported to preserve normal behavior, otherwise stub wallet APIs (createWallet, generateMnemonic returning raw crypto.randomBytes hex, signTransaction) are exposed as cover while the exfiltration has already fired.

Malicious versions

1 flagged

5.4.2

Indicators of compromise (SHA-256)

8981a1bdc42ac6f595b3805c959060201fc4eb0c39b5bf50b25c5d3d7cc398b5

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

Campaign

IN-MAL-2026-015791

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bitcoinjs-wallet-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