Which versions of oaipbyqhfcyqh are malicious?

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

How do I remediate oaipbyqhfcyqh if I installed it?

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

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

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

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

Malicious package

oaipbyqhfcyqhRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8303

Immediate action

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

gem uninstall oaipbyqhfcyqh

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0d1b688da8fb639fc1ad15203049355d48ff576bbad53ae4dd483d0519bc88a9

89ac939d01ba803143613a434acb083e7eccf654189416ab4ca02f1eee3e061a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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