Which versions of python-bitcoinlib are malicious?

The following npm versions of python-bitcoinlib are flagged malicious: 1.0.0, 1.0.1, 1.0.2, 1.0.3. Treat any of these as compromised.

How do I remediate python-bitcoinlib if I installed it?

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

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

Yes — python-bitcoinlib is associated with the IN-MAL-2026-013405, IN-MAL-2026-013414, IN-MAL-2026-013426, IN-MAL-2026-013406 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 python-bitcoinlib 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 python-bitcoinlib (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging python-bitcoinlib across your stack and pipelines.

Malicious package

python-bitcoinlibnpm

python-bitcoinlib is a confirmed malicious npm package (MAL-2026-12113) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.0, 1.0.1, 1.0.2…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in python-bitcoinlib (npm)

MAL-2026-12113

Immediate action

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

npm uninstall python-bitcoinlib

What this malware does

This npm package, published under the well-known PyPI name python-bitcoinlib, ships a postinstall.js lifecycle script that runs automatically on npm install. The script reads classic installer secret paths including ~/.ssh/id_rsa, ~/.aws/credentials, ~/.npmrc, .env files, and Solana/Ethereum wallet keystores (~/.config/solana/id.json), and additionally walks dotdirs under $HOME for files whose names match wallet/key/secret/seed/mnemonic/keystore/private patterns. The collected file contents, together with os.hostname() and os.userInfo(), are POSTed via https.request to a hardcoded webhook.site collector at https://webhook.site/5c5ad6cb-62df-4ea5-9dfb-2c447920ddc4. The package name collides with the established PyPI python-bitcoinlib project but ships unrelated code on npm, indicating deliberate ecosystem-confusion typosquatting rather than a legitimate port.

Malicious versions

4 flagged

1.0.01.0.11.0.21.0.3

Indicators of compromise (SHA-256)

0b40d55f884f1f26d7e0c5b6e21c5d2c3e419ae844f867b6b9cfc73d99f0dc4a

2feaa9ed505ac89313fee83925ae8c3364477c8a468d84810275c7532b92832a

9e6e2d9915baad022b788cee95aed5c00113d2701ca0c690c25ec55016241555

cfb9c83260c4fb83a678636e1e1c028f2aff3e3c0a0ac13728cfa2056a13389f

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

Campaign

IN-MAL-2026-013405IN-MAL-2026-013414IN-MAL-2026-013426IN-MAL-2026-013406

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks python-bitcoinlib-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