Which versions of oaiix9664993 are malicious?

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

How do I remediate oaiix9664993 if I installed it?

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

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

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

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

Malicious package

oaiix9664993RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8239

Immediate action

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

gem uninstall oaiix9664993

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6753c3b312cb12f5a9ba965156717baf81ca84473d5d1cfab935af5ee48bafc5

fb6eb9cc96f91bb75969ea000eb04b8ceed09ce4c21ac9fb31ad9471a6d68a8b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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