Which versions of oakmi17500 are malicious?

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

How do I remediate oakmi17500 if I installed it?

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

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

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

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

Malicious package

oakmi17500RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8405

Immediate action

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

gem uninstall oakmi17500

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3131c345ea699fdd07e10ffcbe5ee47d351cebc3ffb762729a4d609ce0e7022c

50dcc1a183933ac9ad5bf7dc29907f64ee394dc360e80291b42caf9746b85040

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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