Which versions of solnetall are malicious?

The following NuGet versions of solnetall are flagged malicious: 0.0.2, 0.0.3, 0.0.7, 0.0.15, 0.0.18, 0.0.20, 2.56.2, 2.56.3. Treat any of these as compromised.

How do I remediate solnetall if I installed it?

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

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

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

Search your lockfiles and build artifacts for solnetall (8 malicious versions).

Malicious package

solnetallNuGet

Advisory published Dec 1, 2025Updated Dec 2, 2025

solnetall is a confirmed malicious NuGet package (MAL-2025-191613) that executes malicious code on install (malicious versions 0.0.2, 0.0.3, 0.0.7…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in solnetall (NuGet)

MAL-2025-191613

Immediate action

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

remove solnetall

Malicious versions

8 flagged

0.0.20.0.30.0.70.0.150.0.180.0.202.56.22.56.3

Indicators of compromise (SHA-256)

f1ac03eb4a5104af603926f960da8b11aa419bd24c0a97e055a3d3e9d05f3a31

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for solnetall (8 malicious versions).
If you installed it — respond
Remove solnetall 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 solnetall 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. solnetall on NuGet has been identified as a malicious package (versions 0.0.2, 0.0.3, 0.0.7, 0.0.15, 0.0.18, 0.0.20, 2.56.2, 2.56.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05580

Credits

ReversingLabs · finder

Detect & block this

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