Which versions of oaipjupjfdrys are malicious?

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

How do I remediate oaipjupjfdrys if I installed it?

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

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

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

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

Malicious package

oaipjupjfdrysRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8311

Immediate action

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

gem uninstall oaipjupjfdrys

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

55571c864a1ebb197275ccde119e2e2eac6e41bd72fb85725401743fb2891673

2dd5fd82c03b3fa80a1c449613e47ceef7bce6db15f73fbff37c1543210e8381

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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