Which versions of wandscalx are malicious?

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

How do I remediate wandscalx if I installed it?

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

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

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

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

Malicious package

wandscalxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9255

Immediate action

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

gem uninstall wandscalx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0804681095b2127487f3f50cb998caeb4c49e360845bae0d06b38441b2b16157

167e3984f9db9d794658d05fff4fca315fac0352664d10a048fdc02c5e616715

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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