Which versions of oakmi17100 are malicious?

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

How do I remediate oakmi17100 if I installed it?

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

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

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

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

Malicious package

oakmi17100RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8401

Immediate action

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

gem uninstall oakmi17100

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

2cba1acb896a7d5294417123204386baaaf7ae5e3fbf141a4bce52a40aa1fe39

4ec7c0346f430281e2477895453345848e25e83d78b7318ec1f87ab96b65609f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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