Which versions of oailmd are malicious?

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

How do I remediate oailmd if I installed it?

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

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

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

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

Malicious package

oailmdRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8298

Immediate action

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

gem uninstall oailmd

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

62f5634cade84d9148db5007bddb9c1c0fff82b505e5379f9bed3654ca793529

f4e92085f4700341c7aec196a033487b58e5ec897ee323ceb7ba0e4b34390ee7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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