Which versions of oaigx4516770 are malicious?

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

How do I remediate oaigx4516770 if I installed it?

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

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

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

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

Malicious package

oaigx4516770RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8209

Immediate action

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

gem uninstall oaigx4516770

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

780f08c5e12cb2dc349763b98f7db86df5c40597989fcd3f1b9f72f34426d1f7

7cbfcd234f64ad12e25a9b02bcd4338a93d5f8123c63565e516092cf6acb979a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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