Which versions of wandczvof4svn are malicious?

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

How do I remediate wandczvof4svn if I installed it?

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

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

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

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

Malicious package

wandczvof4svnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9171

Immediate action

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

gem uninstall wandczvof4svn

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

52d80bb5b6380bd14aa83a5404abdbdfe8bda0bc62070902eaae56f639758cdc

21ad21babce0ccea83510e22a5e7817e8a6ea336ab9918f346fb3fdd19711808

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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