Which versions of ЅystemLoсk are malicious?

The following NuGet versions of ЅystemLoсk are flagged malicious: 0.0.4. Treat any of these as compromised.

How do I remediate ЅystemLoсk if I installed it?

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

If ЅystemLoсk 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 ЅystemLoсk part of a known attack campaign?

Yes — ЅystemLoсk is associated with the RLMA-2024-02772, RLMA-2026-00002 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 ЅystemLoсk across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for ЅystemLoсk (version 0.0.4).

Malicious package

ЅystemLoсkNuGet

Advisory published Jun 25, 2024Updated Mar 19, 2026

ЅystemLoсk is a confirmed malicious NuGet package (MAL-2024-4718) that executes malicious code on install (malicious version 0.0.4). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in ЅystemLoсk (NuGet)

MAL-2024-4718

Immediate action

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

remove ЅystemLoсk

Malicious versions

1 flagged

0.0.4

Indicators of compromise (SHA-256)

f560e8c615915d805e3d6cc7e48eb6db4355e6772f8b8b759e17470cc56e0d49

3ee7a0e7784a157d7fa9d1affbfb779394552faeebf30430b784e103907d52a2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-02772RLMA-2026-00002

Credits

ReversingLabs · finder

Detect & block this

O3 blocks ЅystemLoсk-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