Which versions of wanddbbehg02 are malicious?

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

How do I remediate wanddbbehg02 if I installed it?

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

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

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

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

Malicious package

wanddbbehg02RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9190

Immediate action

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

gem uninstall wanddbbehg02

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

22aeea5eaee0868ac9a3403644537615ea7e63d632d918a5d75eaae4ba372eef

e985d05c9501e0d3549ff2430b6b63c128884b94afe3d586fa87817a43ff2e03

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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