Which versions of wandhr5 are malicious?

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

How do I remediate wandhr5 if I installed it?

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

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

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

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

Malicious package

wandhr5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9225

Immediate action

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

gem uninstall wandhr5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

382488b335041e19791fa8014d892745cfdae68fc311590fb28fb8f95c6fb29f

34e684631db273420e75fcb94a8fcff86a1bf573f341e6bd87aa709539ace2df

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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