Which versions of oaitbzrxmtfoa are malicious?

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

How do I remediate oaitbzrxmtfoa if I installed it?

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

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

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

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

Malicious package

oaitbzrxmtfoaRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8337

Immediate action

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

gem uninstall oaitbzrxmtfoa

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

87ed8e8573879d115197d127d0ff14e3a9a4fdc5feef4cb61a84131a875b028c

96412a40543c495506c6be68c4f55bc9683a7d4654709bfe51a7bfa490485ba7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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