Which versions of wandhr7 are malicious?

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

How do I remediate wandhr7 if I installed it?

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

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

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

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

Malicious package

wandhr7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9227

Immediate action

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

gem uninstall wandhr7

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1272eabe6d99e43339548ef89f4cd3b812b1beb03616e008f858db4866059df8

985fec5bbba00b23d9cdf21cefcb6764ae28c740b8c8e111c505a95105156605

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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