Which versions of oakmi16600 are malicious?

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

How do I remediate oakmi16600 if I installed it?

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

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

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

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

Malicious package

oakmi16600RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8396

Immediate action

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

gem uninstall oakmi16600

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

65864b6eac4bf4a55910ab2ed88d4204b0ff736a794c4ef5b1b8432a849f055c

8876dad8209748e01bb247700edcdc43ed2befbbf16a228651c306e4be8ca515

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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