Which versions of wanddbbehg05 are malicious?

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

How do I remediate wanddbbehg05 if I installed it?

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

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

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

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

Malicious package

wanddbbehg05RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9193

Immediate action

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

gem uninstall wanddbbehg05

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0158f8810c600e4ea81efd0882fe55fade2fba8a944284853cf8c7559366d008

c2d754187bb3b32ed47142759843dd6eea98e7d97b48aea61a62db3c4048e644

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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