Which versions of oaipefyjwkzmx are malicious?

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

How do I remediate oaipefyjwkzmx if I installed it?

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

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

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

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

Malicious package

oaipefyjwkzmxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8307

Immediate action

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

gem uninstall oaipefyjwkzmx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1224ce6c70d6d0ae594a475dc3c95e8b92539b80353640d3c6bfdbbbc09e7ff0

d4f1ebc00629b0f99d2c981a0d19c73c868b5177722d3f2831f2637376bc4643

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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