Which versions of oaipgttatggxy are malicious?

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

How do I remediate oaipgttatggxy if I installed it?

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

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

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

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

Malicious package

oaipgttatggxyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8309

Immediate action

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

gem uninstall oaipgttatggxy

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1bd5f795d044d6f1f2152413f3338d76c4396dfbece6d9a50805305086a60b89

4739c0e07dd9f9239e49db849a1543006d284fc32343a56445c75ac547190e7b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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