Which versions of bitcoinlibdbfix are malicious?

The following PyPI versions of bitcoinlibdbfix are flagged malicious: 0.4.8, 0.4.9, 0.4.10, 0.4.11, 0.4.12, 0.4.13, 0.4.14. Treat any of these as compromised.

How do I remediate bitcoinlibdbfix if I installed it?

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

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

Yes — bitcoinlibdbfix is associated with the RLMA-2025-02496, 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 bitcoinlibdbfix 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 bitcoinlibdbfix (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bitcoinlibdbfix across your stack and pipelines.

Malicious package

bitcoinlibdbfixPyPI

Malicious code in bitcoinlibdbfix (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2025-3437

Immediate action

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

pip uninstall bitcoinlibdbfix

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

7 flagged

0.4.80.4.90.4.100.4.110.4.120.4.130.4.14

Indicators of compromise (SHA-256)

ab5b3540f4c692cb612450c054a7f3f6269fac09919d37ad47715afa2a314d18

55845c378f8d0c93bb2ac1f5f38bb4a6e226fd3f506cda28e55ce70ee713d052

a5cb52fa4f2ac6a68416c59a513399e01bb388d5e238260b712a513db3d97233

d0a5c5913c23e65a4562411c5623b96364dbcc4baa11648c7efba0e804bec935

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 bitcoinlibdbfix (7 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bitcoinlibdbfix across your stack and pipelines.
If you installed it — respond
bitcoinlibdbfix 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 bitcoinlibdbfix 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 bitcoinlibdbfix 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. bitcoinlibdbfix on PyPI has been identified as a malicious package (versions 0.4.8, 0.4.9, 0.4.10, 0.4.11, 0.4.12, 0.4.13, 0.4.14 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-024962025-03-bitcoinlibdbfix

References

Credits

Kamil Mańkowski (kam193)
ReversingLabs · finder

Detect & block this

O3 blocks bitcoinlibdbfix-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