Which versions of oaipqsobhbexg are malicious?

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

How do I remediate oaipqsobhbexg if I installed it?

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

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

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

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

Malicious package

oaipqsobhbexgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8322

Immediate action

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

gem uninstall oaipqsobhbexg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d87e386162402091025e3eba7063982ddb3093475abb2a190018fd8d3600b8d5

85d5543d23a4d99864079e0112424d7c3f30ac3ddf440dd9204b367dd09f8018

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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