Which versions of wandhcalz are malicious?

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

How do I remediate wandhcalz if I installed it?

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

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

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

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

Malicious package

wandhcalzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9210

Immediate action

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

gem uninstall wandhcalz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b888c2ac228de7246a1db77b3cb3a7b59f37d1cbcdd59da39f40626252ce6b91

09853288b6d89fc5a030416d20d431302825ae75d5d66525b0db681697b14afe

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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