Which versions of oaidx6514197 are malicious?

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

How do I remediate oaidx6514197 if I installed it?

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

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

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

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

Malicious package

oaidx6514197RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8175

Immediate action

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

gem uninstall oaidx6514197

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

902929f2a4a059620d9d4165538c599bea3577fae9f3c98b4693bfd26dc41d86

cf06c14817e5d37e6a8a16f8d8f6236a87c38d117af32cd39ad7b48cb7178d5f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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