Which versions of oaklflic are malicious?

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

How do I remediate oaklflic if I installed it?

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

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

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

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

Malicious package

oaklflicRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8367

Immediate action

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

gem uninstall oaklflic

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a5e6d51bbd10a2ddcc66c2a7a65ca613a19c391033dfbadb3546dcb6ddad87a8

713c2286f907cdf1e6c6fdada9406c409cbe4945113f30784335ca4801229619

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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