Which versions of oaipttacwhdpp are malicious?

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

How do I remediate oaipttacwhdpp if I installed it?

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

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

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

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

Malicious package

oaipttacwhdppRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8325

Immediate action

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

gem uninstall oaipttacwhdpp

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

83d939917a4cbd14587f33dd3403ba90810cbef03b2c844528d0265152de89d5

24c26796101123e052b0882e538a2b591db203a6ea47b2bbcfdf48937e66f4f0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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