Which versions of wandscal2 are malicious?

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

How do I remediate wandscal2 if I installed it?

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

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

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

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

Malicious package

wandscal2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9252

Immediate action

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

gem uninstall wandscal2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c1502a1e11b078df3604d44492ead6be0fb965f14b35c77648566aba9386e4c3

d79f6a7db0f17d18b86e0c4a3a07edb59dcd4be0232dd6a0ef525ade239e5723

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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