Which versions of bitcoinlib-dev are malicious?

The following PyPI versions of bitcoinlib-dev are flagged malicious: 0.4.16, 0.4.17, 0.4.18, 0.4.19, 0.4.20, 0.4.21. Treat any of these as compromised.

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

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.

I already installed bitcoinlib-dev — how do I know if it already compromised me?

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.

Is bitcoinlib-dev part of a known attack campaign?

Yes — bitcoinlib-dev is associated with the RLMA-2025-02495, 2025-03-bitcoinlibdbfix 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 bitcoinlib-dev 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 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.

Malicious package

bitcoinlib-devPyPI

Malicious code in bitcoinlib-dev (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3436

Immediate action

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

pip uninstall bitcoinlib-dev

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

6 flagged

0.4.160.4.170.4.180.4.190.4.200.4.21

Indicators of compromise (SHA-256)

60f9219187ef9ed45dfc3b7c27f27c66f0a32769437a28f83827bad54e7bd624

76ff9fe5768d125b1c73e1502902291a8882bfc28b2b333dde6e10b21b372b95

a198ee5e2df9c67dcbd24ed19a8fec5d462bbb3c0eb474cf00cd299e75074ef5

cab20eb85be911dd4de0c38b292bb096aa60beb2cf67c9c2920b8b1ffbbfb2a2

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 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

No. bitcoinlib-dev on PyPI has been identified as a malicious package (versions 0.4.16, 0.4.17, 0.4.18, 0.4.19, 0.4.20, 0.4.21 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-024952025-03-bitcoinlibdbfix

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.

Malware detection Runtime egress monitoring