Which versions of oaigx1767798 are malicious?

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

How do I remediate oaigx1767798 if I installed it?

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

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

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

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

Malicious package

oaigx1767798RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8208

Immediate action

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

gem uninstall oaigx1767798

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d0719b5a06a71584e90a6ff8b2f76b89de9774300a420553dd3cacfe4c23d8ed

4f649e6209e109abf747f4a8c2947bd9256c14cb9807b2a024ff924876dc8739

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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