Which versions of wandhr8 are malicious?

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

How do I remediate wandhr8 if I installed it?

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

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

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

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

Malicious package

wandhr8RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9228

Immediate action

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

gem uninstall wandhr8

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

67c3b9ed12e9a3596ab864d2e25437d6e6a90d7e6d860e1323e633a12f7cc46e

ba18aa093c761809a94f07cab1803cdf167d7ce214b601485568e9d5ab9d5c9a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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