Which versions of oaidx3879209 are malicious?

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

How do I remediate oaidx3879209 if I installed it?

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

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

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

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

Malicious package

oaidx3879209RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8172

Immediate action

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

gem uninstall oaidx3879209

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6bf0976c99c43393c689a0a094846519f30ef20b4a7cba36a1b892a064473834

7d6994c62e7e9be172c577913d88bf2c69e09888da2e8a776a978abdab91091c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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