Which versions of Nеthеreսm.Sіgner.Lеdgеr are malicious?

The following NuGet versions of Nеthеreսm.Sіgner.Lеdgеr are flagged malicious: 4.16.0. Treat any of these as compromised.

How do I remediate Nеthеreսm.Sіgner.Lеdgеr if I installed it?

Remove Nеthеreսm.Sіgner.Lеdgеr 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 Nеthеreսm.Sіgner.Lеdgеr — how do I know if it already compromised me?

If Nеthеreսm.Sіgner.Lеdgеr 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 Nеthеreսm.Sіgner.Lеdgеr part of a known attack campaign?

Yes — Nеthеreսm.Sіgner.Lеdgеr is associated with the RLMA-2024-03351 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 Nеthеreսm.Sіgner.Lеdgеr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for Nеthеreսm.Sіgner.Lеdgеr (version 4.16.0).

Malicious package

Nеthеreսm.Sіgner.LеdgеrNuGet

Nеthеreսm.Sіgner.Lеdgеr is a confirmed malicious NuGet package (MAL-2024-4580) that executes malicious code on install (malicious version 4.16.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in Nеthеreսm.Sіgner.Lеdgеr (NuGet)

MAL-2024-4580

Immediate action

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

remove Nеthеreսm.Sіgner.Lеdgеr

Malicious versions

1 flagged

4.16.0

Indicators of compromise (SHA-256)

f9b6dc83ff7630bb6f38d1bbeed37ae9cc675929ea4f6382f11de8f72b8f4173

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for Nеthеreսm.Sіgner.Lеdgеr (version 4.16.0).
If you installed it — respond
Remove Nеthеreսm.Sіgner.Lеdgеr 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 Nеthеreսm.Sіgner.Lеdgеr 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. Nеthеreսm.Sіgner.Lеdgеr on NuGet has been identified as a malicious package (version 4.16.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03351

Credits

ReversingLabs · finder

Detect & block this

O3 blocks Nеthеreսm.Sіgner.Lеdgеr-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