Which versions of wagwn3bothab are malicious?

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

How do I remediate wagwn3bothab if I installed it?

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

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

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

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

Malicious package

wagwn3bothabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9131

Immediate action

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

gem uninstall wagwn3bothab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

07c741a6738db69c1e3d60866783e497af55900e5e8215ce4d89ba326a038310

3c518c02acbc9669613a31bc643838b6a79a68ad8313cbc8608b3c49d000b19e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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