Which versions of oakmi16100 are malicious?

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

How do I remediate oakmi16100 if I installed it?

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

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

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

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

Malicious package

oakmi16100RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8391

Immediate action

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

gem uninstall oakmi16100

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

30468f247bf264eea60c7e035650662e9653163854d91a23c53d0d2e3697fbdd

b3f9fe87fb55683335837013ef8e520998b5603b694d0d63d461bc7c65be2f41

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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