Which versions of oaikx8326270 are malicious?

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

How do I remediate oaikx8326270 if I installed it?

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

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

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

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

Malicious package

oaikx8326270RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8279

Immediate action

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

gem uninstall oaikx8326270

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

208dc20bff4ff7d9e60db1177f2b98ecf0aac3c1ca0b8d87ace879535ba80af2

313124dc887289bfd95ab05983b8e3fb01dff3641bc110ea929f7ea8fd6aae3e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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