Which versions of oailm7 are malicious?

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

How do I remediate oailm7 if I installed it?

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

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

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

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

Malicious package

oailm7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8292

Immediate action

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

gem uninstall oailm7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e96f8be632cb034ed65703bae9d77deb34d19bdd68cef9973a300427a11fb383

87cd75c0ea27611956b5d367d4e9dbb4c2683587b1a632d88ef7f727b6184a43

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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