Which versions of oakmi16200 are malicious?

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

How do I remediate oakmi16200 if I installed it?

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

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

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

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

Malicious package

oakmi16200RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8392

Immediate action

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

gem uninstall oakmi16200

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

facee18febda5601848cd3422ae318f85d363959122cd27cf5dbe086cc6bd18f

eb8dd0a488fa8b7db8e6cf6663e0e32e47b5c14a5d2523a9fcc92746c434b17e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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