Which versions of SЅ.CМS are malicious?

The following NuGet versions of SЅ.CМS are flagged malicious: 6.15.51. Treat any of these as compromised.

How do I remediate SЅ.CМS if I installed it?

Remove SЅ.CМS 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 SЅ.CМS — how do I know if it already compromised me?

If SЅ.CМS 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 SЅ.CМS part of a known attack campaign?

Yes — SЅ.CМS is associated with the RLMA-2024-03420, RLMA-2026-00022 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 SЅ.CМS across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for SЅ.CМS (version 6.15.51).

Malicious package

SЅ.CМSNuGet

Advisory published Jun 25, 2024Updated Mar 19, 2026

SЅ.CМS is a confirmed malicious NuGet package (MAL-2024-4672) that executes malicious code on install (malicious version 6.15.51). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in SЅ.CМS (NuGet)

MAL-2024-4672

Immediate action

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

remove SЅ.CМS

Malicious versions

1 flagged

6.15.51

Indicators of compromise (SHA-256)

969248aba7bfe2ed48a995a082f7206d814d9e7d01c52b09b94663d0153aece0

ee1e47cf2843e2bd5ecde78492adedd0e5037d87e3e966cfa4fe6991e4f906b5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for SЅ.CМS (version 6.15.51).
If you installed it — respond
Remove SЅ.CМS 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 SЅ.CМS 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. SЅ.CМS on NuGet has been identified as a malicious package (version 6.15.51 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-03420RLMA-2026-00022

Credits

ReversingLabs · finder

Detect & block this

O3 blocks SЅ.CМS-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