Which versions of wandqhack0 are malicious?

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

How do I remediate wandqhack0 if I installed it?

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

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

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

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

Malicious package

wandqhack0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9247

Immediate action

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

gem uninstall wandqhack0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

02b266ea0e5ca05fd6690987f926e85ba0d811234668a211146db2b60845ac59

0dbe59d0066a416bfb527d05708c4aa7fbee58c540dd75d26a4336d39114f16e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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