Which versions of oaklfjan0 are malicious?

The following RubyGems versions of oaklfjan0 are flagged malicious: 0.0.31807. Treat any of these as compromised.

How do I remediate oaklfjan0 if I installed it?

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

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

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

Search your lockfiles and build artifacts for oaklfjan0 (version 0.0.31807).

Malicious package

oaklfjan0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in oaklfjan0 (RubyGems)

MAL-2026-8357

Immediate action

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

gem uninstall oaklfjan0

Malicious versions

1 flagged

0.0.31807

Indicators of compromise (SHA-256)

8d6c0a1da42b3ea7199533330d28970c496dcea29515c0a587ec84b19bd52bff

f0a88507655c949382ca43ec6346ebb8dcbaa1a5760a774f8826160309a41224

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03008RLUA-2026-08872

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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