Which versions of wandcalh are malicious?

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

How do I remediate wandcalh if I installed it?

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

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

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

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

Malicious package

wandcalhRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9142

Immediate action

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

gem uninstall wandcalh

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4274380e0ce0c00eaad2c7c7aa9d7b403c06e003263c93f7ce6027754b53cf84

d526f1eaffb68c24dffeeba3e4a119aeeb80aad094c21ca528dad7265f88d2b0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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