Which versions of oaijhgmzryzc are malicious?

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

How do I remediate oaijhgmzryzc if I installed it?

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

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

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

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

Malicious package

oaijhgmzryzcRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8257

Immediate action

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

gem uninstall oaijhgmzryzc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4cd1c85065fad6c19588b9ec621244fc784e17615af4c751a9c702945d9e7db4

f195cee6271b69e9d15756d5e9a2526e7c193047dd5e3e076356358a1b1f6d3a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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