Which versions of wagwn2txtab are malicious?

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

How do I remediate wagwn2txtab if I installed it?

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

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

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

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

Malicious package

wagwn2txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9130

Immediate action

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

gem uninstall wagwn2txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c55a1bcf40ac0be0d58c1389bb1c7881cef2406c7ea15e15c4b71901c8c56bc1

393e7d25615acc17833cfc2112e60c1b4e960a2e529d5085ea868b78c6f27fab

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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