Which versions of oaiex1182709 are malicious?

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

How do I remediate oaiex1182709 if I installed it?

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

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

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

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

Malicious package

oaiex1182709RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8179

Immediate action

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

gem uninstall oaiex1182709

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

29474bf09c38947c139c6d04bf35e390420744124e4da3a9dbf5ddfb3ad6fb03

9537bd27a7fefece7577a4a400c69ec496eb02823ba6e6b939af9f84b73756ee

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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