Which versions of wandhgenc are malicious?

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

How do I remediate wandhgenc if I installed it?

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

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

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

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

Malicious package

wandhgencRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9213

Immediate action

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

gem uninstall wandhgenc

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b63c4b307bf3ad2ebb52449a1d6c2b253251c6d21c34ae15d41756242a0fa706

290d25d3653f194a015ab6a0bcbe764175ad626e423b8fd432f7c7f421ff3730

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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