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

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

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

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

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

Yes — @zzzgenesis00/bitcoin-lib is associated with the IN-MAL-2026-014393 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 @zzzgenesis00/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 @zzzgenesis00/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 @zzzgenesis00/bitcoin-lib across your stack and pipelines.

Malicious package

@zzzgenesis00/bitcoin-libnpm

@zzzgenesis00/bitcoin-lib is a confirmed malicious npm package (MAL-2026-12118) 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 @zzzgenesis00/bitcoin-lib (npm)

MAL-2026-12118

Immediate action

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

npm uninstall @zzzgenesis00/bitcoin-lib

What this malware does

@zzzgenesis00/bitcoin-lib 6.1.7 runs a postinstall.js at npm install time that harvests installer-owned secrets and exfiltrates them to attacker-controlled destinations. The script enumerates ~/.ssh, reads ~/.npmrc and ~/.gitconfig, inventories Chrome/Firefox cookie and login stores, scans cryptocurrency wallet directories (.bitcoin,.ethereum,.metamask, Exodus, Electrum, and others), and captures a curated list of credential-shaped environment variables including NPM_TOKEN, NODE_AUTH_TOKEN, GITHUB_TOKEN, AWS_*, *_PRIVATE_KEY, MNEMONIC, and SEED_PHRASE. Collected data is JSON-serialized and sent, after a short setTimeout delay, via GET to api.telegram.org/bot<TOKEN>/sendMessage with a hardcoded chat_id and via POST /collect to 40f955f39128bd79-178-249-214-24.serveousercontent.com. The package.json falsely attributes authorship to 'bitcoinjs' and points the repository at github.com/bitcoinjs/bitcoin-lib, impersonating the well-known bitcoinjs organization while shipping under the unrelated @zzzgenesis00 scope.

Malicious versions

1 flagged

6.1.7

Indicators of compromise (SHA-256)

742be73b4f635f669a2c8191ddc90c46150e9d92ca432e5045c570fc0163f439

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 @zzzgenesis00/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 @zzzgenesis00/bitcoin-lib across your stack and pipelines.
If you installed it — respond
@zzzgenesis00/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 @zzzgenesis00/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 @zzzgenesis00/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. @zzzgenesis00/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-014393

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks @zzzgenesis00/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