Which versions of oaipaqfeefizk are malicious?

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

How do I remediate oaipaqfeefizk if I installed it?

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

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

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

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

Malicious package

oaipaqfeefizkRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8301

Immediate action

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

gem uninstall oaipaqfeefizk

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9b21193959c049ba1552ed0afb39bdeb5426845cbd8838f5525a876a22809230

86e9ce922829110a0a80bd7890f0012bae71a1818408ff6c9531d689058a2ee1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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