Which versions of oaipefrlkaloi are malicious?

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

How do I remediate oaipefrlkaloi if I installed it?

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

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

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

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

Malicious package

oaipefrlkaloiRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8306

Immediate action

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

gem uninstall oaipefrlkaloi

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

844a3503623b6ce6f39fca4b711be2d363e815a619b06099b68a1dec64b7d5b2

543392915108297aea6a026e7b5e2871c4a6142aa93925ce47421ac8cef595d8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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