Which versions of oaidx3492001 are malicious?

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

How do I remediate oaidx3492001 if I installed it?

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

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

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

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

Malicious package

oaidx3492001RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8171

Immediate action

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

gem uninstall oaidx3492001

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f43876aa302855f750cafc03f9b97507dea2927a170290dd62021566375b1eea

3c1fd0e2da7cff3e303aee72af439fb8141a2d36e81b273cf0b520a4f3fa9287

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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