Which versions of fig-rake are malicious?

The following RubyGems versions of fig-rake are flagged malicious: 0.9.3. Treat any of these as compromised.

How do I remediate fig-rake if I installed it?

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

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

Yes — fig-rake is associated with the RLMA-2024-05700, RLUA-2024-10219, RLUA-2026-08082 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 fig-rake across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for fig-rake (version 0.9.3).

Malicious package

fig-rakeRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

fig-rake is a confirmed malicious RubyGems package (MAL-2024-6894) that executes malicious code on install (malicious version 0.9.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in fig-rake (RubyGems)

MAL-2024-6894

Immediate action

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

gem uninstall fig-rake

Malicious versions

1 flagged

0.9.3

Indicators of compromise (SHA-256)

972cbdc3502b3d88526698e2ceeaaf9494afa08abd0b52c97bf8dbdc3ccc15d1

b01476b878c92b45e51860af6c36df392aa55963ce19d0ea7c1997c1021eb0e9

d4c3092fa1d8973d62417fbbb0bdd99b2ca1bcbe0ba269db8fc22a9d388621a5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05700RLUA-2024-10219RLUA-2026-08082

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks fig-rake-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