Which versions of oaiex0549290 are malicious?

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

How do I remediate oaiex0549290 if I installed it?

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

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

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

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

Malicious package

oaiex0549290RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8178

Immediate action

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

gem uninstall oaiex0549290

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

464d1958b699e672ffbbcfa20acebf33b6776eea5f69360b8746f7e0f15512f6

e0cdbf0b5c2d2c0d26eaaeebb86423c2b91e5d55eda9f31d017b9af8c81e26ae

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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