Which versions of oaipkesbgrrqn are malicious?

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

How do I remediate oaipkesbgrrqn if I installed it?

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

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

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

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

Malicious package

oaipkesbgrrqnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8312

Immediate action

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

gem uninstall oaipkesbgrrqn

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

17ede0b3b46459a702967ae84ae43ee385fcb00f46c81a8f3fe976e3627d450f

47f1e0d090b184268b926cb2c94d06b6c955bef08897bb28641d770dd200dc6d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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