bitcoinlib-devPyPI
bitcoinlib-dev is a confirmed malicious PyPI package (MAL-2025-3436) that steals credentials and exfiltrates sensitive data (malicious versions 0.4.16, 0.4.17, 0.4.18…). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in bitcoinlib-dev (PyPI)
What this malware does
It overwrites the 'clw' command from legit bitconinlib package and attempts to exfiltrate its database on the usage.
As a context, it appears to be created to lure users seeking for help with the bitconinlib package: https://github.com/1200wd/bitcoinlib/issues/455#issuecomment-2764513104
Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.
Campaign: 2025-03-bitcoinlibdbfix
Reasons (based on the campaign):
-
files-exfiltration
-
crypto-related
-
action-hidden-in-lib-usage
-
exfiltration-crypto
Malicious versions
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bitcoinlib-dev (6 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bitcoinlib-dev across your stack and pipelines.
If you installed it — respond
bitcoinlib-dev 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 bitcoinlib-dev 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 bitcoinlib-dev 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
Campaign
References
Credits
- Kamil Mańkowski (kam193)
- ReversingLabs · finder
Detect & block this
O3 blocks bitcoinlib-dev-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.