Which versions of oakmi15200 are malicious?

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

How do I remediate oakmi15200 if I installed it?

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

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

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

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

Malicious package

oakmi15200RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8382

Immediate action

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

gem uninstall oakmi15200

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

385ab0399d65f534248d699cd9cb406c311e6c1ef68b723303d242dca3f4997d

8e077b96d819b6d9e4ea3cae5485233f4dd83c3e58c40847635858a50f38743d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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