Which versions of oaklfjan1 are malicious?

The following RubyGems versions of oaklfjan1 are flagged malicious: 0.0.61639. Treat any of these as compromised.

How do I remediate oaklfjan1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for oaklfjan1 (version 0.0.61639).

Malicious package

oaklfjan1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in oaklfjan1 (RubyGems)

MAL-2026-8358

Immediate action

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

gem uninstall oaklfjan1

Malicious versions

1 flagged

0.0.61639

Indicators of compromise (SHA-256)

4ccf4d7f186406261bcf6519dc8225177b909519bc27c664f435ef4177256ed1

04701557b88e490ab7638d25b6ca4131fa859588f81f18f8741f598bf070c186

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03009RLUA-2026-08873

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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