Which versions of oaiix7006631 are malicious?

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

How do I remediate oaiix7006631 if I installed it?

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

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

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

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

Malicious package

oaiix7006631RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8235

Immediate action

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

gem uninstall oaiix7006631

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cfc3f43716d286998e6fb3636f1c1583617f14d814b03560b635e8f75f22afd2

a2b9e264aa0e34740a75279258135bc28ff23d608a7c8aef08b21c0660ff212e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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