Which versions of oailma are malicious?

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

How do I remediate oailma if I installed it?

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

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

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

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

Malicious package

oailmaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8295

Immediate action

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

gem uninstall oailma

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b6827cf74b97a01211c4570ff56c9061667dbfc1a7bdc4cf141c76494acadce9

ddd40649cfe9e51bc9348b89d5280eb6f5527d8ca286b25ddca1ce55e00fea36

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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