Which versions of wandhgx are malicious?

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

How do I remediate wandhgx if I installed it?

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

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

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

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

Malicious package

wandhgxRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9216

Immediate action

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

gem uninstall wandhgx

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

257a6b3d5267a0b2eb6dfc7035e05703226e77af5829e13ade8620ea3a6a05e9

16c5b2f33d3242e170d3aa8f3d9035c387c12085d19e65531c57212115c462ba

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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