Which versions of wagwn6bothab are malicious?

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

How do I remediate wagwn6bothab if I installed it?

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

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

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

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

Malicious package

wagwn6bothabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9137

Immediate action

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

gem uninstall wagwn6bothab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a05d24fccfa1ecd7ed627dcf39e0f1bf8e8eda4497fae6a6bd8cd90523f91b13

41dd1b0a86fe01d287bbcce9223dde0602b9a0c81b2a155470f4602b4c9ebee5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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