Which versions of oakmi15500 are malicious?

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

How do I remediate oakmi15500 if I installed it?

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

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

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

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

Malicious package

oakmi15500RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8385

Immediate action

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

gem uninstall oakmi15500

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

88a421959bad9020df132babeed5e622b559c1123806dd0c4be794db50fee399

954292a3ac100e9a59152cf6234fd876d55333094402c1232d10e7f6c9b502c1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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