Which versions of wandqhack1 are malicious?

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

How do I remediate wandqhack1 if I installed it?

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

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

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

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

Malicious package

wandqhack1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9248

Immediate action

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

gem uninstall wandqhack1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

79e9fff1cd63977b0e52bc634e828d571a933454a3b60af818c34d4769b8e81e

693b9412cb64441682c16b3bb966f3667b49e534f4485d72cb2095ed6b27ad49

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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