Which versions of oaipmxktcwywo are malicious?

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

How do I remediate oaipmxktcwywo if I installed it?

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

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

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

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

Malicious package

oaipmxktcwywoRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8315

Immediate action

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

gem uninstall oaipmxktcwywo

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

abbab39938c58ef2ca2ed3bfff3c69b05fd7e1487a7433e51302bf047dd3dfdb

aab638caf14596e4d6a2ec30eb36e6089e163694c74309a16dbd3edbc1a3f88a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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