Which versions of solananet are malicious?

The following NuGet versions of solananet are flagged malicious: 0.0.0, 0.0.3, 0.0.13, 0.0.14, 1.56.1, 1.56.2, 1.56.3, 1.56.4. Treat any of these as compromised.

How do I remediate solananet if I installed it?

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

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

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

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

Malicious package

solananetNuGet

Advisory published Dec 1, 2025Updated Dec 2, 2025

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

Malicious code in solananet (NuGet)

MAL-2025-191612

Immediate action

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

remove solananet

Malicious versions

8 flagged

0.0.00.0.30.0.130.0.141.56.11.56.21.56.31.56.4

Indicators of compromise (SHA-256)

b464b2a0e8455a2885b9ce0b859fc4d7760a4f1081a054f9955be819c4ee2c33

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for solananet (8 malicious versions).
If you installed it — respond
Remove solananet 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 solananet 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. solananet on NuGet has been identified as a malicious package (versions 0.0.0, 0.0.3, 0.0.13, 0.0.14, 1.56.1, 1.56.2, 1.56.3, 1.56.4 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-05579

Credits

ReversingLabs · finder

Detect & block this

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