Which versions of divining-rod are malicious?

The following RubyGems versions of divining-rod are flagged malicious: 0.6.4. Treat any of these as compromised.

How do I remediate divining-rod if I installed it?

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

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

Yes — divining-rod is associated with the RLMA-2024-05669, RLUA-2024-10188, RLUA-2026-07977 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 divining-rod across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for divining-rod (version 0.6.4).

Malicious package

divining-rodRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

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

Malicious code in divining-rod (RubyGems)

MAL-2024-6863

Immediate action

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

gem uninstall divining-rod

Malicious versions

1 flagged

0.6.4

Indicators of compromise (SHA-256)

145f9c6931d068af88ccfc5919603d2ee12a61ade08ab4908c5fd58ae4d32587

c9ef3236bbd97457f9caaa3983592aa3bcb5832fa545bdd6d38b6d43b8f18890

97500162eb264395916f1d62faaf3bbd097ca7f501bc9793faf4a531d427521a

Detection & response playbook

Malicious package

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

Campaign

RLMA-2024-05669RLUA-2024-10188RLUA-2026-07977

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks divining-rod-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