Which versions of wagwn5bothab are malicious?

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

How do I remediate wagwn5bothab if I installed it?

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

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

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

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

Malicious package

wagwn5bothabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9135

Immediate action

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

gem uninstall wagwn5bothab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7450a3189ca2f7027980b4116906b41c68a17fa5bf345d85e5812d977ede54ce

ab8374ef9fe0197bd29a753f50fe99996e3043a00146f0286958d836cd82bc5c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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