Which versions of wandqhack2 are malicious?

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

How do I remediate wandqhack2 if I installed it?

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

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

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

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

Malicious package

wandqhack2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9249

Immediate action

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

gem uninstall wandqhack2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

48adb0b2341807b8ea97fb7b194c379dce1ea3fb13b482d79d001d1d9a2720b5

f7333ba146b20adf353f62e8021909078eae9de2e2eb9fabc98f45a3e7eeda84

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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