Which versions of wandshack9 are malicious?

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

How do I remediate wandshack9 if I installed it?

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

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

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

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

Malicious package

wandshack9RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9282

Immediate action

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

gem uninstall wandshack9

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

81d2b4f8a03edf434204fa1342eab46148ff92af870b46bc16476fd67f94ed47

16336d19b792718386f6e21b14e766461bfc36139b919843483ad839fe47d8b7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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