Which versions of wwandhg are malicious?

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

How do I remediate wwandhg if I installed it?

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

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

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

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

Malicious package

wwandhgRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9494

Immediate action

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

gem uninstall wwandhg

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4d29c4c0890d0dce1b2eea6a8edfc3a3f19d2e3803e5bd07b3cbf65ce17106a1

f64962b6ab409de4a2be854330f0c399d3b8ca51ccf0df3687be8d124b25c677

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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