Which versions of wandczvof4hg are malicious?

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

How do I remediate wandczvof4hg if I installed it?

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

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

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

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

Malicious package

wandczvof4hgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9170

Immediate action

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

gem uninstall wandczvof4hg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4dc0e084bf2043e8ceb31300d760cad45cca3ad5a9f4fbe2fb6ba9fa4152449b

a387eae8288debac31052f5f9f65f381c1a100b9c8d8d9e734d2fb9c25467303

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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