Which versions of oakmi15300 are malicious?

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

How do I remediate oakmi15300 if I installed it?

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

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

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

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

Malicious package

oakmi15300RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8383

Immediate action

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

gem uninstall oakmi15300

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6fefe17ec593fce37ab197b0074b1dff1f185a7bd074655350dfe5c4321f473e

0ed83dba6f8163faff2ee07e37f061fc8838636b21502ea2308fb21cdaab4b9d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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