Which versions of oaidx4526859 are malicious?

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

How do I remediate oaidx4526859 if I installed it?

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

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

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

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

Malicious package

oaidx4526859RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8173

Immediate action

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

gem uninstall oaidx4526859

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d4bcb36ffe97295f85ef6330adb05c7bd093354f46b03456d1870f47322665f5

75760dd81d3bed90c7dbd4d28156f6c037d4a1e8791da85c2ae51084e5c303b3

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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