Which versions of oaibootx8192 are malicious?

The following RubyGems versions of oaibootx8192 are flagged malicious: 0.0.1, 0.0.2, 0.0.3. Treat any of these as compromised.

How do I remediate oaibootx8192 if I installed it?

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

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

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

Search your lockfiles and build artifacts for oaibootx8192 (3 malicious versions).

Malicious package

oaibootx8192RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

oaibootx8192 is a confirmed malicious RubyGems package (MAL-2026-8152) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in oaibootx8192 (RubyGems)

MAL-2026-8152

Immediate action

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

gem uninstall oaibootx8192

Malicious versions

3 flagged

0.0.10.0.20.0.3

Indicators of compromise (SHA-256)

d02f057347dd7730408579ff538e67c90f7a729220a6da78cd863f1eca3b5f9e

f767db03a200c536722b0f19b2f04aab06af7754fd2269daaa13d60b5b1165e8

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for oaibootx8192 (3 malicious versions).
If you installed it — respond
Remove oaibootx8192 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 oaibootx8192 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. oaibootx8192 on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-02803RLUA-2026-08667

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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