Which versions of oakmi15100 are malicious?

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

How do I remediate oakmi15100 if I installed it?

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

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

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

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

Malicious package

oakmi15100RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8381

Immediate action

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

gem uninstall oakmi15100

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

093daadc9b43f23fc3934388c4aa4895f7ba44a026a3a7a1bd6546ba32c2ae0b

9060b702bb481bfb066b790369886cef2807c546db3f807d49db3a83c33ea018

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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