Which versions of oaikx8889218 are malicious?

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

How do I remediate oaikx8889218 if I installed it?

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

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

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

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

Malicious package

oaikx8889218RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8281

Immediate action

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

gem uninstall oaikx8889218

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

47d36b51502dc040f1d78069094fac83827e9a58ef9129783f8c9887069274f7

9a46ad3462ffc8b1a87f0a9b5dc3203404641f40a4ff4ff456aed56179fd29db

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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