Which versions of oaitgitxrclle are malicious?

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

How do I remediate oaitgitxrclle if I installed it?

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

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

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

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

Malicious package

oaitgitxrclleRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8345

Immediate action

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

gem uninstall oaitgitxrclle

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

58e70add4589b289587704510dfd987d802e9bbaea51a99d5fd1e4f6ae66e3a8

8be9bedd05fa4d37eed984b6386bd6e55834c3e8aed95714478d002da0de173e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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