Which versions of forgiving-nil are malicious?

The following RubyGems versions of forgiving-nil are flagged malicious: 0.0.2. Treat any of these as compromised.

How do I remediate forgiving-nil if I installed it?

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

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

Yes — forgiving-nil is associated with the RLMA-2024-05729, RLUA-2024-10248, RLUA-2026-08114 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 forgiving-nil across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for forgiving-nil (version 0.0.2).

Malicious package

forgiving-nilRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

forgiving-nil is a confirmed malicious RubyGems package (MAL-2024-6923) that executes malicious code on install (malicious version 0.0.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in forgiving-nil (RubyGems)

MAL-2024-6923

Immediate action

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

gem uninstall forgiving-nil

Malicious versions

1 flagged

0.0.2

Indicators of compromise (SHA-256)

d4419226ff06b71dd075cf1625e1e430953233f2cdfae446548953f6ec10b2e8

2bf13eded199d638435905d8306cf97216719882878a9e8f6024373fc296a4d4

ea605678162a431cf31d0e8ae424cfd2b0c2dbbd8449d2978d8083ee8f34e268

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05729RLUA-2024-10248RLUA-2026-08114

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks forgiving-nil-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