Which versions of oaidx1169327 are malicious?

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

How do I remediate oaidx1169327 if I installed it?

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

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

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

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

Malicious package

oaidx1169327RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8166

Immediate action

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

gem uninstall oaidx1169327

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

eee14062eaa35bede3db5eabe3bd222350d7613ce74bec9a32c6379f5ee17779

a56275e536f972eb18c894c17b61377377d2bfc3f04003679c3a952d1bab7fad

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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