Which versions of oaiex0014506 are malicious?

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

How do I remediate oaiex0014506 if I installed it?

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

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

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

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

Malicious package

oaiex0014506RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8177

Immediate action

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

gem uninstall oaiex0014506

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3231cf8138b7a99b450b6bbbf0401fece3bc81a0bc155dd23faaab86e5ace7e8

3185d6aa47e86a67bab96f1a7cd3296c62cb8f02b09609cc3d81d28317d803c2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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