Which versions of wagwn3txtab are malicious?

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

How do I remediate wagwn3txtab if I installed it?

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

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

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

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

Malicious package

wagwn3txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9132

Immediate action

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

gem uninstall wagwn3txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

caccb8be297991d8a2f47007eb09e9aaefddafb670415aaa9aaef5ef03e8ff94

a6fc7756ed64035deb115e2ad91238bbdd7f51ba4ff404c01ae88fd0bbb698e0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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