Which versions of wandhgpath are malicious?

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

How do I remediate wandhgpath if I installed it?

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

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

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

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

Malicious package

wandhgpathRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9214

Immediate action

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

gem uninstall wandhgpath

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5dd546170cea79b73628e4cb3006e0a76da7e6332c9b191baee31142a1114e29

6684050c4c6115830d427087a262993d679be2e64822582d1d6c110378c698da

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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