Which versions of oailm9 are malicious?

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

How do I remediate oailm9 if I installed it?

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

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

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

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

Malicious package

oailm9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8294

Immediate action

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

gem uninstall oailm9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

814705438f0c330ec6d378fa1ea6408a57f2ee9e4a9923b1c43c79b1abf1afcf

6dc8ccc65db11b5a43514123edf56e216a920921049d7b4b1653b7ec6bedbcd3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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