Which versions of oaidx1466937 are malicious?

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

How do I remediate oaidx1466937 if I installed it?

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

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

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

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

Malicious package

oaidx1466937RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8168

Immediate action

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

gem uninstall oaidx1466937

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4f2ed17db0fe0c6cd5ff9923083001effb2df0be4fee24b6be2245b1e545c1c9

cffa057ff2adb6ba2805dbee2c36856a40cba14e2f72dbd413ebe30de186aabb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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