Which versions of wandhr2 are malicious?

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

How do I remediate wandhr2 if I installed it?

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

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

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

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

Malicious package

wandhr2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9222

Immediate action

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

gem uninstall wandhr2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

dc5653d898e5d65f50bb94f6e454f2e13c67a5ad7c9b9c533daece45bf521a8f

2b535e18170f6891d85a8f9e0c8cce848577ecda55d0c08f9005ce8c8550c068

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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