Which versions of wandshack6 are malicious?

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

How do I remediate wandshack6 if I installed it?

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

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

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

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

Malicious package

wandshack6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9279

Immediate action

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

gem uninstall wandshack6

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

be2b5aaf5b627622ea87a68381e4f666ea660d1355f2af50bbb0ec89662c8e02

c1a695415fb3add3dc667cd2e038c4b55f5a5df1ee3365b936b83f752e5da5fc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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