Which versions of bitcoincore are malicious?

The following NuGet versions of bitcoincore are flagged malicious: 0.0.4, 0.0.9, 0.0.13, 0.0.18, 0.0.22, 1.0.24, 1.0.25. Treat any of these as compromised.

How do I remediate bitcoincore if I installed it?

Remove bitcoincore from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed bitcoincore — how do I know if it already compromised me?

If bitcoincore was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is bitcoincore part of a known attack campaign?

Yes — bitcoincore is associated with the RLMA-2025-05572 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 bitcoincore across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bitcoincore (7 malicious versions).

Malicious package

bitcoincoreNuGet

Advisory published Dec 1, 2025Updated Dec 2, 2025

bitcoincore is a confirmed malicious NuGet package (MAL-2025-191605) that executes malicious code on install (malicious versions 0.0.4, 0.0.9, 0.0.13…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bitcoincore (NuGet)

MAL-2025-191605

Immediate action

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

remove bitcoincore

Malicious versions

7 flagged

0.0.40.0.90.0.130.0.180.0.221.0.241.0.25

Indicators of compromise (SHA-256)

57ce6b475ab373cd7bc27a7dc045ed2a2438fdfe998f530eaf6884a40efbc05b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bitcoincore (7 malicious versions).
If you installed it — respond
Remove bitcoincore from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bitcoincore was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. bitcoincore on NuGet has been identified as a malicious package (versions 0.0.4, 0.0.9, 0.0.13, 0.0.18, 0.0.22, 1.0.24, 1.0.25 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05572

Credits

ReversingLabs · finder

Detect & block this

O3 blocks bitcoincore-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database