Which versions of oaiix5537218 are malicious?

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

How do I remediate oaiix5537218 if I installed it?

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

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

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

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

Malicious package

oaiix5537218RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8234

Immediate action

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

gem uninstall oaiix5537218

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5d56f6c699ab3f788739118ab39bba248f96baf754424a1df17403763a517b5c

e1ddb730cf9a831be4f115df782976b87d9ef718e648445ee41a3f82ecf31910

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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