Which versions of oaipttxrgucrm are malicious?

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

How do I remediate oaipttxrgucrm if I installed it?

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

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

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

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

Malicious package

oaipttxrgucrmRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8326

Immediate action

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

gem uninstall oaipttxrgucrm

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e4b39382eff3e51d8b9ff0eb5cdb8b0466d28b23e0c786ab393df64501871713

effb68eabd2284b2050664028107951633947136946bbd619169c7038e4cf2e9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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