Which versions of oaiix3669509 are malicious?

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

How do I remediate oaiix3669509 if I installed it?

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

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

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

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

Malicious package

oaiix3669509RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8231

Immediate action

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

gem uninstall oaiix3669509

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e132a1bd3228805ac53bb41c578c8474d21f1bb614da55e5b97f235686fef68b

846ac6d141ebeabf498110983abf5e41c93160bff48b9c8af4378e8c4b973d50

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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