Which versions of oaipyvtoeydiu are malicious?

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

How do I remediate oaipyvtoeydiu if I installed it?

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

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

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

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

Malicious package

oaipyvtoeydiuRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8334

Immediate action

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

gem uninstall oaipyvtoeydiu

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d693ed7f09e6c522fe1dc89d92b5ee4bb3e67b832fc9a4e3cfe366a99f89dd72

38bab2e4212febada4577ed86ec76a606b63a913503447adff9480c0b04e9cf5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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