Which versions of oakmi15000 are malicious?

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

How do I remediate oakmi15000 if I installed it?

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

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

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

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

Malicious package

oakmi15000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8380

Immediate action

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

gem uninstall oakmi15000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bf04908193fd0771df86fb8db2076fefc27c1c0f4180cd1a059f38920ac458cf

a6cced0f3d2abe716a751b0133e170f14bc2ce25973363a8044e3507128497ae

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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