Which versions of wandhgcal are malicious?

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

How do I remediate wandhgcal if I installed it?

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

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

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

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

Malicious package

wandhgcalRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9212

Immediate action

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

gem uninstall wandhgcal

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a3edeb0d7b006e31f6899623417e6be56eaf7295b1705b0ab99d3e04f06db7dd

890037c20de59ce29b2180711cc472c7a012adc45da655e26cb01756a5748a7b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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