Which versions of oaklfjan4 are malicious?

The following RubyGems versions of oaklfjan4 are flagged malicious: 0.0.74826. Treat any of these as compromised.

How do I remediate oaklfjan4 if I installed it?

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

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

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

Search your lockfiles and build artifacts for oaklfjan4 (version 0.0.74826).

Malicious package

oaklfjan4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in oaklfjan4 (RubyGems)

MAL-2026-8361

Immediate action

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

gem uninstall oaklfjan4

Malicious versions

1 flagged

0.0.74826

Indicators of compromise (SHA-256)

ce872e46051e9a044379fe58948e709659c643fc1871a5091fd2c6518fd61fe3

6daa34cc057c2c08a27e1c37d90b64d4e25f510a6d59ba45ee6a62ff2de811c2

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03012RLUA-2026-08876

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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