Which versions of oaidx3409275 are malicious?

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

How do I remediate oaidx3409275 if I installed it?

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

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

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

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

Malicious package

oaidx3409275RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8170

Immediate action

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

gem uninstall oaidx3409275

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dfc0ca6fd9a4f012594c628150e2687de585d950a9b63e7eccaad9bcbc1e323b

d4e2188c185810816cd341731a3ed2de3913a446c0a0869d2498c2e7e6098978

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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