Which versions of oakmi17300 are malicious?

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

How do I remediate oakmi17300 if I installed it?

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

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

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

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

Malicious package

oakmi17300RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8403

Immediate action

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

gem uninstall oakmi17300

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

848b842c8ec9c3d5e49f1afef59c71bf10b97fdfb93bc1019fd916151a589a72

9da6fc7d85116332c4cf60259b4f1741f61c18efba41872abe34f1070d2c6518

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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