Which versions of oaklfjan2 are malicious?

The following RubyGems versions of oaklfjan2 are flagged malicious: 0.0.22753. Treat any of these as compromised.

How do I remediate oaklfjan2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for oaklfjan2 (version 0.0.22753).

Malicious package

oaklfjan2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in oaklfjan2 (RubyGems)

MAL-2026-8359

Immediate action

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

gem uninstall oaklfjan2

Malicious versions

1 flagged

0.0.22753

Indicators of compromise (SHA-256)

04591a8adbe05429d4626378be3ea5587c704aee52f91d01b593c5fc3b53eb2b

35d68a1233d61f6611c944097916c072ed0ec4f7c4bb128a58dd35e1353b5ae3

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03010RLUA-2026-08874

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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