Which versions of oaibootz9218 are malicious?

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

How do I remediate oaibootz9218 if I installed it?

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

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

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

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

Malicious package

oaibootz9218RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8154

Immediate action

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

gem uninstall oaibootz9218

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1674fe618e6029c236e4d4ee72b4c9f16b8f60232b18c93844da36105311d769

2823b823f0844daa61de76d4d8776f2f7a812dd3e53b7a413be5c2c76f40a284

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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