Which versions of wagwn5txtab are malicious?

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

How do I remediate wagwn5txtab if I installed it?

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

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

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

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

Malicious package

wagwn5txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9136

Immediate action

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

gem uninstall wagwn5txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9702123b558ffde9e11f28c7f85fae4372a8e6cc1d15d35dfbbd6faa3f37dad1

bb3622e4b33cbc22d30d48c08378d2c742f02af8a2f8661ce3837e520976ef15

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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