Which versions of oakmi16500 are malicious?

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

How do I remediate oakmi16500 if I installed it?

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

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

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

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

Malicious package

oakmi16500RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8395

Immediate action

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

gem uninstall oakmi16500

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dfe0782927cc142a76783e4ff42f8220d86a0a86dbe98278b483e351652405c4

1dc12cd1f9969f9f59f506a618aa58afcbc930339c1437f32120d8812e489e0b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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