Which versions of wandhr11 are malicious?

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

How do I remediate wandhr11 if I installed it?

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

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

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

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

Malicious package

wandhr11RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9220

Immediate action

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

gem uninstall wandhr11

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a2ab46c095b05caf4d7eacc700c175fe8633c1f7c39a598b3ab42340dffcdb56

de95733200943b08e3f16939a00eacec3a3cadf98085d94cbb4afab546f48f00

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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