Which versions of oaidx0276239 are malicious?

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

How do I remediate oaidx0276239 if I installed it?

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

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

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

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

Malicious package

oaidx0276239RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8165

Immediate action

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

gem uninstall oaidx0276239

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ee674ed85c7caa686dd01ef1330867edcd11fae49575647a5a2773e588169b7f

c065e8af06d7d56569955b230f145d3f10f7052b2fb0dfdf2cc4e5fa977cf0e9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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