Which versions of dt_rake are malicious?

The following RubyGems versions of dt_rake are flagged malicious: 0.0.3. Treat any of these as compromised.

How do I remediate dt_rake if I installed it?

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

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

Yes — dt_rake is associated with the RLMA-2024-05684, RLUA-2024-10203, RLUA-2026-08022 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 dt_rake across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for dt_rake (version 0.0.3).

Malicious package

dt_rakeRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in dt_rake (RubyGems)

MAL-2024-6878

Immediate action

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

gem uninstall dt_rake

Malicious versions

1 flagged

0.0.3

Indicators of compromise (SHA-256)

d8108a17a01334b0bf4762a43a0df993757018d1852275847a77f8d9f83180d1

097e8560b3ffe89987b0af88c6618f925e2976e3f6b6fe00c474758c5e8a1ef8

13ee48ce87a60efff542a9e541b6acb46336f5aea6b989fcc5a88a1bbd68f7da

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05684RLUA-2024-10203RLUA-2026-08022

References

Credits

ReversingLabs · finder

Detect & block this

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