Which versions of oaikx2502114 are malicious?

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

How do I remediate oaikx2502114 if I installed it?

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

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

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

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

Malicious package

oaikx2502114RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8275

Immediate action

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

gem uninstall oaikx2502114

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d82215f2e65e7575ffcf62b51d320f29e4b625110e4f4ddba5c46ba07b1e591b

559fd7706fd1fa123592cb424c8caf1ee775f635b3c2445aff1d3b03a82722a1

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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