Which versions of oaijbzrgtxirk are malicious?

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

How do I remediate oaijbzrgtxirk if I installed it?

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

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

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

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

Malicious package

oaijbzrgtxirkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8243

Immediate action

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

gem uninstall oaijbzrgtxirk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9cc1bd811a9d24bd376e2bf4e1410c2a245fde8062751dbc9e0496203163c890

7255df899c951ef2ff3d967b9e6a0c406d38ee24954c8df59ca1ba59fc0a2572

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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