Which versions of oaipojrqrusxl are malicious?

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

How do I remediate oaipojrqrusxl if I installed it?

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

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

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

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

Malicious package

oaipojrqrusxlRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8318

Immediate action

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

gem uninstall oaipojrqrusxl

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9d3317d5192855c53c04f5ba55c911e7a8ba960a7146ba2e1295f04a56493ba8

9945c31e489847b4bdd683bd3c8990358c3beee312555f5d3150c99f44945a3c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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