Which versions of okra are malicious?

The following RubyGems versions of okra are flagged malicious: 0.900.0, 1.900, 8.0.0, 16, 90002.0. Treat any of these as compromised.

How do I remediate okra if I installed it?

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

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

Yes — okra is associated with the RLMA-2024-05803, RLUA-2024-10324, RLUA-2026-08926 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 okra across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for okra (5 malicious versions).

Malicious package

okraRubyGems

Advisory published Jun 25, 2024Updated Sep 24, 2026

okra is a confirmed malicious RubyGems package (MAL-2024-6997) that executes malicious code on install (malicious versions 0.900.0, 1.900, 8.0.0…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in okra (RubyGems)

MAL-2024-6997

Immediate action

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

gem uninstall okra

Malicious versions

5 flagged

0.900.01.9008.0.01690002.0

Indicators of compromise (SHA-256)

063dc45b43ad935c4e68e0d84fe105d36d5ff36a51cc71b539ba7d8b917a5ff3

cb87626be4fed5904b38f40c6e6ab0d8341ba6622d1d5dac54d8d09e749a0703

c355575908e189449013fd51c1d6882541aebc1b5113fb61b14e76d65b94a9e3

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for okra (5 malicious versions).
If you installed it — respond
Remove okra 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 okra 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. okra on RubyGems has been identified as a malicious package (versions 0.900.0, 1.900, 8.0.0, 16, 90002.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2024-05803RLUA-2024-10324RLUA-2026-08926

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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