Which versions of wandshack5 are malicious?

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

How do I remediate wandshack5 if I installed it?

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

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

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

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

Malicious package

wandshack5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9278

Immediate action

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

gem uninstall wandshack5

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8c6f05f35dde712e7919c5492a5d8bda7e1caa4735da60af3a74d02b400a9265

70dab3aeeb53ad9891b26fcc567d75b305af48d23e93a2a188cec5c76d9bd96c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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