Which versions of oaigx5861576 are malicious?

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

How do I remediate oaigx5861576 if I installed it?

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

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

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

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

Malicious package

oaigx5861576RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8212

Immediate action

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

gem uninstall oaigx5861576

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7b26aaa9fecc3f390f28de222021c57b3181f2c063aa7ddd9e57439eb70a81a0

5de1632a77c57f43f7960ee7333112e9b5bf07e4ca2f1ae171ad55d3b92651cc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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