Which versions of oaixhgdpvkpij are malicious?

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

How do I remediate oaixhgdpvkpij if I installed it?

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

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

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

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

Malicious package

oaixhgdpvkpijRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8353

Immediate action

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

gem uninstall oaixhgdpvkpij

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d87349528927b0ec42003bf6c83edaf02f758f7cc649e1bcb095f784fb904b30

3b5bd4f500d3bc8ab29cb5cf155f42455aa7fa9c0eea42e8db721c21f55994c8

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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