Which versions of oakmi16900 are malicious?

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

How do I remediate oakmi16900 if I installed it?

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

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

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

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

Malicious package

oakmi16900RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8399

Immediate action

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

gem uninstall oakmi16900

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3246a51b430388c3518236d0c8ddd97627f90d82a3e2059233acf798c25d530c

628cf0c5ff0b540064b3e54bfe889ac5ae81ff70e22da39a4a4f073124724a24

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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