Which versions of wandhr10 are malicious?

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

How do I remediate wandhr10 if I installed it?

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

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

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

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

Malicious package

wandhr10RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9219

Immediate action

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

gem uninstall wandhr10

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a68dd268f90f599289ec174753cce76a707f4a6873af94b1ea827781b4d32b1c

97df480bb75bf0134cf90afc16c399fb4e20b0fe483080c10159a4f7d3d50019

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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