Which versions of oaklfplan are malicious?

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

How do I remediate oaklfplan if I installed it?

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

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

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

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

Malicious package

oaklfplanRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

oaklfplan is a confirmed malicious RubyGems package (MAL-2026-8369) 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 oaklfplan (RubyGems)

MAL-2026-8369

Immediate action

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

gem uninstall oaklfplan

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b6c15633f851882c959f3729d215806a34fc011968ccd59caca9a3e2574ecd78

7891bbd41ce381185aff56da7cf20ce7728e2e12e009173b1a22a01995133bd9

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for oaklfplan (version 0.0.1).
If you installed it — respond
Remove oaklfplan 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 oaklfplan 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. oaklfplan 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-03020RLUA-2026-08884

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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