Which versions of nethereumunified are malicious?

The following NuGet versions of nethereumunified are flagged malicious: 0.0.4, 0.0.11, 0.0.15, 0.0.18, 0.0.39, 0.0.59, 0.0.63, 0.0.97, 0.0.98, 0.0.107, 0.0.113, 0.0.117, 5.0.0, 5.1.0, 5.2.0, 5.3.0, 6.0.0. Treat any of these as compromised.

How do I remediate nethereumunified if I installed it?

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

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

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

Search your lockfiles and build artifacts for nethereumunified (17 malicious versions).

Malicious package

nethereumunifiedNuGet

Advisory published Dec 1, 2025Updated Dec 2, 2025

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

Malicious code in nethereumunified (NuGet)

MAL-2025-191610

Immediate action

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

remove nethereumunified

Malicious versions

17 flagged

0.0.40.0.110.0.150.0.180.0.390.0.590.0.630.0.970.0.980.0.1070.0.1130.0.1175.0.05.1.05.2.05.3.06.0.0

Indicators of compromise (SHA-256)

277e3931e20df8e1128fa8860f705b4c80dbe0a52e4de086dd98b2defb2cfd92

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for nethereumunified (17 malicious versions).
If you installed it — respond
Remove nethereumunified 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 nethereumunified 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. nethereumunified on NuGet has been identified as a malicious package (versions 0.0.4, 0.0.11, 0.0.15, 0.0.18, 0.0.39, 0.0.59, 0.0.63, 0.0.97, and 9 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05578

Credits

ReversingLabs · finder

Detect & block this

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