Which versions of wanddbbehg01 are malicious?

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

How do I remediate wanddbbehg01 if I installed it?

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

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

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

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

Malicious package

wanddbbehg01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9189

Immediate action

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

gem uninstall wanddbbehg01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c7132c0ed50bde8bc3d26d56ac0e1ca562349971913e2e53e4090d54409c83db

8294bee4d77141b2f1d7fc3792193bf11fc4183c0866f81568d14ad9782fe674

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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