Which versions of oaklfcom are malicious?

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

How do I remediate oaklfcom if I installed it?

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

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

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

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

Malicious package

oaklfcomRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8356

Immediate action

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

gem uninstall oaklfcom

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0540fcfb7337dec28492929f8ba02a6063ca9d0a60855a2cf469d25f2738d297

9301edf5e178684ee8d2ebfa0dddedc604472ab7513734ab424ea02b1224cfcd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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