Which versions of oaigx9094125 are malicious?

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

How do I remediate oaigx9094125 if I installed it?

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

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

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

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

Malicious package

oaigx9094125RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8215

Immediate action

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

gem uninstall oaigx9094125

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cb25a1571a4ceee367064e23e716efa9ab128b5c0076fb3f0226970e3839b61c

f79cd997dbe051fda4e02155aedc518e88955eef5ba1aad49c669597b7a2432d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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