Which versions of wandshack3 are malicious?

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

How do I remediate wandshack3 if I installed it?

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

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

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

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

Malicious package

wandshack3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9276

Immediate action

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

gem uninstall wandshack3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

34a674578bb5ab9440ec3abff89e4b914834258389a8ffdc711b71c07e368f13

41c824eac43ed97959299e435aaae2281d6324403430427d9c3713f119e2e4e0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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