Which versions of wandstest-c217d0 are malicious?

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

How do I remediate wandstest-c217d0 if I installed it?

wandstest-c217d0 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed wandstest-c217d0 — how do I know if it already compromised me?

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

Yes — wandstest-c217d0 is associated with the RLMA-2026-03944, RLUA-2026-09874 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 wandstest-c217d0 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wandstest-c217d0 (version 0.0.1).

Malicious package

wandstest-c217d0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

wandstest-c217d0 is a confirmed malicious RubyGems package (MAL-2026-9293) that opens a backdoor for remote access (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wandstest-c217d0 (RubyGems)

MAL-2026-9293

Immediate action

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

gem uninstall wandstest-c217d0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

10099d9aba5ca01e7fa8131fcd77a9373f6cee51912299303a3a023702db9693

1267b10c5e24a096ebdd280d18f6cc763808125827ed9be4c9ed7a3bcffeb621

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for wandstest-c217d0 (version 0.0.1).
If you installed it — respond
wandstest-c217d0 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If wandstest-c217d0 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. wandstest-c217d0 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-03944RLUA-2026-09874

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks wandstest-c217d0-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database