Which versions of oakmi17900 are malicious?

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

How do I remediate oakmi17900 if I installed it?

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

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

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

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

Malicious package

oakmi17900RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8409

Immediate action

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

gem uninstall oakmi17900

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

96d66a1aa0874f88b77c7b6fd8758ee722097ef9d1ba896afe906a82cf88b1e3

eefd133c324ea51bfe99dd1e2aef0d3399096bb169667db0ebcb16c3981042cd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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