Which versions of oaiix7984341 are malicious?

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

How do I remediate oaiix7984341 if I installed it?

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

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

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

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

Malicious package

oaiix7984341RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8237

Immediate action

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

gem uninstall oaiix7984341

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9c8133861c37f40079d7521d2cfe66bcf5f44f6df5f883da2709185f017c8159

84f46eb25101a7e2c97ba05870fbd3ce9d5819ecfaa78930b42837a0aeb4708e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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