Which versions of oaipmfgnywddt are malicious?

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

How do I remediate oaipmfgnywddt if I installed it?

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

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

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

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

Malicious package

oaipmfgnywddtRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8314

Immediate action

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

gem uninstall oaipmfgnywddt

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d0114dbc62793c3833d001a0a9fd331e21b004898e080601d99f23433e23afea

1f98cd8907ee1733592aa6be0eee4fd3ddb4f8156af9cfe15321cdf62db8e2f8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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