Which versions of wandhr0 are malicious?

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

How do I remediate wandhr0 if I installed it?

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

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

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

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

Malicious package

wandhr0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9217

Immediate action

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

gem uninstall wandhr0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

82beca600b60b07e321b4b9addbad6eb3f8e8e9f9307801471a369bfddec309d

93bb15c5eb9782c289970c04983d52b4e272cefc1bdfadaaea2f49cf1451272b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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