Which versions of oakmi15900 are malicious?

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

How do I remediate oakmi15900 if I installed it?

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

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

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

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

Malicious package

oakmi15900RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8389

Immediate action

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

gem uninstall oakmi15900

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3a93321e9247806b5e23aa2d03399235ef9529d893e6444415b8afdb3f1dcf18

26b43771c14b433b268f21e28615f300101e1c8fcc009f08df5c53dff4040b9e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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