Which versions of wandsvnx are malicious?

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

How do I remediate wandsvnx if I installed it?

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

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

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

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

Malicious package

wandsvnxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9295

Immediate action

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

gem uninstall wandsvnx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5470f3b5f9abd19b4c6ad4d44c6a88068fd4ada61074ecb636541d3bf77bfd8b

e3edaa95a778d35acbfda1f90a618e031378bfdb0b0866894665d44042a18b6c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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