Which versions of oaklfcab are malicious?

The following RubyGems versions of oaklfcab are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate oaklfcab if I installed it?

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

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

Yes — oaklfcab is associated with the RLMA-2026-03006, RLUA-2026-08870 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 oaklfcab across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for oaklfcab (version 0.0.1).

Malicious package

oaklfcabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

oaklfcab is a confirmed malicious RubyGems package (MAL-2026-8355) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in oaklfcab (RubyGems)

MAL-2026-8355

Immediate action

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

gem uninstall oaklfcab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

32b86bff53fb9f7bd55dccf8b5062441b6d0d16d188e5040ef807febfea1881c

a08f2d3da2138b6b26b6482da591ac7aec5da0b0d9c4a57d863f666554272a18

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03006RLUA-2026-08870

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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