Which versions of @zzzcrypto/bitcoin-lib are malicious?

The following npm versions of @zzzcrypto/bitcoin-lib are flagged malicious: 6.1.7. Treat any of these as compromised.

How do I remediate @zzzcrypto/bitcoin-lib if I installed it?

@zzzcrypto/bitcoin-lib 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 @zzzcrypto/bitcoin-lib — how do I know if it already compromised me?

If @zzzcrypto/bitcoin-lib 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 @zzzcrypto/bitcoin-lib part of a known attack campaign?

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

Malicious package

@zzzcrypto/bitcoin-libnpm

@zzzcrypto/bitcoin-lib is a confirmed malicious npm package (MAL-2026-13211) that steals credentials and exfiltrates sensitive data (malicious version 6.1.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @zzzcrypto/bitcoin-lib (npm)

MAL-2026-13211

Immediate action

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

npm uninstall @zzzcrypto/bitcoin-lib

What this malware does

On require(), index.js serializes process.env together with hostname, username, homedir, platform, cwd, and a timestamp, base64-encodes the JSON, and sends it via HTTPS GET to api.telegram.org using a hardcoded bot token and chat_id. A tmp flag file gates re-execution to reduce noise. The package name @zzzcrypto/bitcoin-lib and its README present it as a drop-in for bitcoinjs-lib, and the code attempts require('bitcoinjs-lib') to transparently proxy the real library's API when present so callers observe normal behavior; the internal identifier in the exfil payload is @wethenorth12/bitcoin-lib, and identifier names in the harvester are scrambled (kffr, xqyv, qzph, _h). Environment variables in developer and CI processes routinely contain credentials, API tokens, and cloud keys, so this constitutes credential and host-identity theft against any process that imports the package.

Malicious versions

1 flagged

6.1.7

Indicators of compromise (SHA-256)

f9d633d3efb27db376be57d77ebbd808db458d088503adebe2f7ad7501281dd1

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

Campaign

IN-MAL-2026-015736

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzcrypto/bitcoin-lib-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