Which versions of wagwn1bothab are malicious?

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

How do I remediate wagwn1bothab if I installed it?

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

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

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

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

Malicious package

wagwn1bothabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9127

Immediate action

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

gem uninstall wagwn1bothab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3c53ef0f4facf1d0bc7954d193c5c68962a8ff357e21d860bd86530e69e25cb5

1b095ae64667c66167c5e5d0175958582232bdef03ea5ed9833e2739cb7e217f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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