Which versions of wandshack1 are malicious?

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

How do I remediate wandshack1 if I installed it?

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

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

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

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

Malicious package

wandshack1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9274

Immediate action

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

gem uninstall wandshack1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

141339801c7a9813ca3c4aa3175c07d31843d5762f0cf9179c661229dfd158e4

7a5331df8a9f8d13dda07c1e9d1f0c761e4dc07322ffc42b8f3d4fba38989300

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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