Which versions of wanddbbehg06 are malicious?

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

How do I remediate wanddbbehg06 if I installed it?

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

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

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

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

Malicious package

wanddbbehg06RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9194

Immediate action

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

gem uninstall wanddbbehg06

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b79dae806351e9f42eba832ff6033feac88a3388b925e7fa251a64dbc2410b24

d6f10f02946c553886729580b57b9235c1ae94c816fb6a86e71fee31d3360cc2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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