Which versions of oailm1 are malicious?

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

How do I remediate oailm1 if I installed it?

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

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

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

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

Malicious package

oailm1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8286

Immediate action

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

gem uninstall oailm1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c44949536baf5b5a9d805ba0ca4a19b2e225b807d4a5bff08d384b688e80ff81

28ff1e29588342a1efba56611d1568e425c53d0685a89d275db46e6d1b40e071

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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