Which versions of oaikx2706764 are malicious?

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

How do I remediate oaikx2706764 if I installed it?

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

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

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

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

Malicious package

oaikx2706764RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8276

Immediate action

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

gem uninstall oaikx2706764

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6265f7688272d2f336d45a603a87ae244600aa179fbbe00a7dfca8f43168cf39

b7ea43c9727dbfea8631b32e0e9999ae1b62421f83b9c7d888c0e4d89f3713e7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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