Which versions of wagwn4bothab are malicious?

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

How do I remediate wagwn4bothab if I installed it?

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

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

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

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

Malicious package

wagwn4bothabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9133

Immediate action

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

gem uninstall wagwn4bothab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

19bd8f2a9519572ce0f6e751be49387726de0c04c441287cc8d8340a47004dc3

b4ae5c5e4d533f99dda408952c5612bef9c1fe5f5d74dd5d0179974eec3bf364

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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