Which versions of oakmi17000 are malicious?

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

How do I remediate oakmi17000 if I installed it?

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

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

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

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

Malicious package

oakmi17000RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8400

Immediate action

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

gem uninstall oakmi17000

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3baf2e290e5db24930ad5fc39b9b30458b9f13d4a58b97599da3fee128a511f4

22504f52f1907447473a3da9f5ae755b6edd7f7846fc4b042e135c2ae9ef200f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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