Which versions of oaklfjan5 are malicious?

The following RubyGems versions of oaklfjan5 are flagged malicious: 0.0.85338. Treat any of these as compromised.

How do I remediate oaklfjan5 if I installed it?

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

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

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

Search your lockfiles and build artifacts for oaklfjan5 (version 0.0.85338).

Malicious package

oaklfjan5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in oaklfjan5 (RubyGems)

MAL-2026-8362

Immediate action

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

gem uninstall oaklfjan5

Malicious versions

1 flagged

0.0.85338

Indicators of compromise (SHA-256)

8a09e2f4b6e84663702d021db4f8aafc1242d6511f113d0b7eb3ae9709a4c109

2fc83bb4840c84359c4a496fb0eae6d38049edcf4811446d6c0d2e331cc3e201

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03013RLUA-2026-08877

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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