Which versions of wandshack7 are malicious?

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

How do I remediate wandshack7 if I installed it?

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

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

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

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

Malicious package

wandshack7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9280

Immediate action

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

gem uninstall wandshack7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

821eb3b4fdc8a7aa1f5187e485b2877648e137cf538ea6a78f4d1f8f4fe6896a

f452fdaf29e7fd79c893ee7b9bac9da449433fb1dde9d67ddac31bc262a03257

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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