Which versions of GetRekt420 are malicious?

The following NuGet versions of GetRekt420 are flagged malicious: 0.9.7. Treat any of these as compromised.

How do I remediate GetRekt420 if I installed it?

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

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

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

Search your lockfiles and build artifacts for GetRekt420 (version 0.9.7).

Malicious package

GetRekt420NuGet

GetRekt420 is a confirmed malicious NuGet package (MAL-2024-4497) that executes malicious code on install (malicious version 0.9.7). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in GetRekt420 (NuGet)

MAL-2024-4497

Immediate action

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

remove GetRekt420

Malicious versions

1 flagged

0.9.7

Indicators of compromise (SHA-256)

d7703680ff2a453c648221381657e95886e03913c5d5bcaaa5e1ae7788c6aee9

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-03286

Credits

ReversingLabs · finder

Detect & block this

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