Which versions of wagwn4txtab are malicious?

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

How do I remediate wagwn4txtab if I installed it?

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

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

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

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

Malicious package

wagwn4txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9134

Immediate action

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

gem uninstall wagwn4txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

ef44a3fb50f41c74629589c0bceba10cb5be5f6df5b50d5515161a4d94899ef6

662086fcf5c7a156f763faf2705b6f9a43ad186b786ab43e01634be19053d041

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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