Which versions of oaklfjan9 are malicious?

The following RubyGems versions of oaklfjan9 are flagged malicious: 0.0.65232. Treat any of these as compromised.

How do I remediate oaklfjan9 if I installed it?

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

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

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

Search your lockfiles and build artifacts for oaklfjan9 (version 0.0.65232).

Malicious package

oaklfjan9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in oaklfjan9 (RubyGems)

MAL-2026-8366

Immediate action

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

gem uninstall oaklfjan9

Malicious versions

1 flagged

0.0.65232

Indicators of compromise (SHA-256)

d3a722557bcfa07fe56f8df7a774b9c328a7aca48a58ccb3b3cee7941ea5a2b5

bb3546f01029880c14de0842afc960a3be150e7f4c97311733a81d416ead908b

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03017RLUA-2026-08881

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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