Which versions of oaiix0360536 are malicious?

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

How do I remediate oaiix0360536 if I installed it?

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

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

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

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

Malicious package

oaiix0360536RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8227

Immediate action

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

gem uninstall oaiix0360536

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5f842a15eaf4b8122298cb35cfa560de12a5cb83f02452cbf34c51cbce8a7537

a4b2807727786bf149ad1e0f44f6518e17de28d2305c3e4ec7c83a9b1fc6ca19

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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