Which versions of wanddbbe01 are malicious?

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

How do I remediate wanddbbe01 if I installed it?

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

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

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

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

Malicious package

wanddbbe01RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9188

Immediate action

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

gem uninstall wanddbbe01

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b52a405f994f70f956b65cfe9c9ed1165fcf3278ffb758015c46c653f76f57bb

14c392b4d1a2ae480ea798c881de93e4f1571656dec76e40505752ace152a069

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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