Which versions of wandfetchhackhg are malicious?

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

How do I remediate wandfetchhackhg if I installed it?

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

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

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

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

Malicious package

wandfetchhackhgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9199

Immediate action

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

gem uninstall wandfetchhackhg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3f2549bb7ae1ae367926747c8605cef0e5c8fc6d91886641870ebe7607c54455

b1a3acf4165edbb11a41f778a7c8a05d993844d52c3e16922c4908aef4f58e9a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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