Which versions of oaiix4070985 are malicious?

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

How do I remediate oaiix4070985 if I installed it?

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

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

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

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

Malicious package

oaiix4070985RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8232

Immediate action

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

gem uninstall oaiix4070985

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0842ffba722063aafb7d34d0802037feb253168b25af6822383a78ef922cef84

ce7e3bf746de458deab6e679f0c4611207dc623aecbefcad5c6dbb747b1b86cd

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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