Which versions of wandhr12 are malicious?

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

How do I remediate wandhr12 if I installed it?

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

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

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

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

Malicious package

wandhr12RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9221

Immediate action

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

gem uninstall wandhr12

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7e4efc50b77ffaf1fa61895988805a4a9f567df16525fce95e31a7e00c76d34a

38213a8b3cbf0186c9c5f987c9047953f7470b76c3f4ec535f5dc01dfefe0436

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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