Which versions of oaiex3222069 are malicious?

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

How do I remediate oaiex3222069 if I installed it?

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

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

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

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

Malicious package

oaiex3222069RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8180

Immediate action

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

gem uninstall oaiex3222069

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b4bf7655f5544f64fdbaa5b7f714afef3ed85983a1fad8c456ebd2f221b1c235

6a1271d865b8ca2e98c4d395344c56fb7319d50808dba1663cbed31e23cb5db6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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