Which versions of wagwn2bothab are malicious?

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

How do I remediate wagwn2bothab if I installed it?

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

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

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

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

Malicious package

wagwn2bothabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9129

Immediate action

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

gem uninstall wagwn2bothab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9d3a7263e475327d445624e5931579998151580b60c76494ae5de87f63e0241a

962dd307b32db4afabb8611f377e181182d1053112746ed7908add48a21a90b5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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