Which versions of security_hacks are malicious?

The following NuGet versions of security_hacks are flagged malicious: 9999.0.0. Treat any of these as compromised.

How do I remediate security_hacks if I installed it?

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

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

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

Search your lockfiles and build artifacts for security_hacks (version 9999.0.0).

Malicious package

security_hacksNuGet

Advisory published Jul 7, 2026Updated Jul 9, 2026

security_hacks is a confirmed malicious NuGet package (MAL-2026-7450) that executes malicious code on install (malicious version 9999.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in security_hacks (NuGet)

MAL-2026-7450

Immediate action

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

remove security_hacks

Malicious versions

1 flagged

9999.0.0

Indicators of compromise (SHA-256)

b89a83fd5bbce8b99588e67c47cf95e241074d8b697d61d24f768e79f7047a06

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-02093

Credits

ReversingLabs · finder

Detect & block this

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