Which versions of oaiex9823513 are malicious?

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

How do I remediate oaiex9823513 if I installed it?

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

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

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

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

Malicious package

oaiex9823513RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8186

Immediate action

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

gem uninstall oaiex9823513

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f50d3fcdeb2289f0a12d2a7e324aa851583312c3930c847275c3f8e11e12c8c2

c587644fe94198583c5cbd7b6141996ef0c3d00422bed19b21eb2527b379dec2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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