Which versions of wandfetchhackx are malicious?

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

How do I remediate wandfetchhackx if I installed it?

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

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

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

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

Malicious package

wandfetchhackxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9201

Immediate action

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

gem uninstall wandfetchhackx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a1f1cc0e62aabf6ca8b16c4385b1acff27533e9f61ca4603b362cd9c8bf7dee8

ab68c375a53daa8337ef96e553db69ca18c35135cf947491d716a15301d0d080

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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