Which versions of oaipnldvhihwd are malicious?

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

How do I remediate oaipnldvhihwd if I installed it?

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

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

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

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

Malicious package

oaipnldvhihwdRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-8316

Immediate action

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

gem uninstall oaipnldvhihwd

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

635d6f0349c3d1bb612818f876ef71c3c89f7cc1322a60c1aa45bf0e4300fddd

32633c50588689f516ddc5813d88e2fbc1e18e5e28e4f1f5cef3ad108cfe2a23

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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