Which versions of oaipbxmwzyrjk are malicious?

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

How do I remediate oaipbxmwzyrjk if I installed it?

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

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

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

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

Malicious package

oaipbxmwzyrjkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8302

Immediate action

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

gem uninstall oaipbxmwzyrjk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9afc32a7aa15855c7406e84b3f87d2fd2a00e113d64629ddcfc3c56725dc783e

e92d5edea5c4f1d7c802a2f80e734523352ae066d5cd6629d0b4404abfc6b967

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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