Which versions of oaklfwk4 are malicious?

The following RubyGems versions of oaklfwk4 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate oaklfwk4 if I installed it?

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

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

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

Search your lockfiles and build artifacts for oaklfwk4 (version 0.0.1).

Malicious package

oaklfwk4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in oaklfwk4 (RubyGems)

MAL-2026-8374

Immediate action

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

gem uninstall oaklfwk4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

167773be7e26f854962760e3b174c9109a812b205528537a9128f33ff988b155

98af22f647824636af0a76cb0499e3d8c3995d1b99017875f498b75a2977f251

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-03025RLUA-2026-08889

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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