Which versions of oakmi15800 are malicious?

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

How do I remediate oakmi15800 if I installed it?

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

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

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

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

Malicious package

oakmi15800RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8388

Immediate action

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

gem uninstall oakmi15800

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

67a61360a9f8239710eb220bd0936f59210af7cdc95d0e9735f8e4e10a643cdb

fa13747685f7428a48c7641570c65f4cb4e5bc02f5c4248a927653c7f04c6041

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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