Which versions of oakmi16700 are malicious?

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

How do I remediate oakmi16700 if I installed it?

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

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

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

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

Malicious package

oakmi16700RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8397

Immediate action

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

gem uninstall oakmi16700

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7b4e8f95dba1e712e6a0c475692fa90108b7b44f4f92973b038ab317758631ff

d42a4af888d657201ebe8ef4da9ad33aebd9c340fa0a901106684d5bba5e815b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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