Which versions of oaijbzrqtntsq are malicious?

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

How do I remediate oaijbzrqtntsq if I installed it?

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

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

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

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

Malicious package

oaijbzrqtntsqRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8244

Immediate action

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

gem uninstall oaijbzrqtntsq

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

28c604674d2eb6ea71e6018d7e82ffc370f106337e9310daa625924091572f88

e163bd0e2d159e560664f34f775aaa58a3e6d401c64839f4fe0b6881f6f22193

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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