Which versions of nbitcoin.unified are malicious?

The following NuGet versions of nbitcoin.unified are flagged malicious: 0.0.25, 0.0.31, 0.0.46, 0.0.70, 0.0.95, 0.0.100, 0.0.114, 0.0.137, 0.0.149, 1.2.6, 1.2.7. Treat any of these as compromised.

How do I remediate nbitcoin.unified if I installed it?

Remove nbitcoin.unified 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 nbitcoin.unified — how do I know if it already compromised me?

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

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

Search your lockfiles and build artifacts for nbitcoin.unified (11 malicious versions).

Malicious package

nbitcoin.unifiedNuGet

Advisory published Dec 1, 2025Updated Dec 2, 2025

nbitcoin.unified is a confirmed malicious NuGet package (MAL-2025-191609) that executes malicious code on install (malicious versions 0.0.25, 0.0.31, 0.0.46…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nbitcoin.unified (NuGet)

MAL-2025-191609

Immediate action

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

remove nbitcoin.unified

Malicious versions

11 flagged

0.0.250.0.310.0.460.0.700.0.950.0.1000.0.1140.0.1370.0.1491.2.61.2.7

Indicators of compromise (SHA-256)

1e7b17034510e80a8ae0a3e1a4bef9ecce2d4983e6a673f012133a65d327d853

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nbitcoin.unified (11 malicious versions).
If you installed it — respond
Remove nbitcoin.unified 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 nbitcoin.unified 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. nbitcoin.unified on NuGet has been identified as a malicious package (versions 0.0.25, 0.0.31, 0.0.46, 0.0.70, 0.0.95, 0.0.100, 0.0.114, 0.0.137, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05576

Credits

ReversingLabs · finder

Detect & block this

O3 blocks nbitcoin.unified-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