Which versions of wandhr3 are malicious?

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

How do I remediate wandhr3 if I installed it?

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

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

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

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

Malicious package

wandhr3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9223

Immediate action

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

gem uninstall wandhr3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

45e3930d4a2d81c0783573c4d7b62c0b0f676d2eb1078208ec3225c241eb74e6

7bbf4a462c3c2f7feb0f0456c5ca8fdf28b5c34d20e4dfe71a85b831993890da

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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