Which versions of oaklfwk9 are malicious?

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

How do I remediate oaklfwk9 if I installed it?

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

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

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

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

Malicious package

oaklfwk9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

oaklfwk9 is a confirmed malicious RubyGems package (MAL-2026-8379) 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 oaklfwk9 (RubyGems)

MAL-2026-8379

Immediate action

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

gem uninstall oaklfwk9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9d5581f8c93f51454041eae137fd45eb64c62bde930e69d9f3fd1170b83d946f

35f49fb43371bd7bfe4108be6bb31b04db7004132cd1da55e139f430ec183b2e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for oaklfwk9 (version 0.0.1).
If you installed it — respond
Remove oaklfwk9 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 oaklfwk9 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. oaklfwk9 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-03030RLUA-2026-08894

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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