Which versions of wmwk1txtab are malicious?

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

How do I remediate wmwk1txtab if I installed it?

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

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

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

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

Malicious package

wmwk1txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9386

Immediate action

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

gem uninstall wmwk1txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

02ebdb964d53edd42bfa6cb37069aa323eefa99c794141c6a0c5520815000fb2

8ad852abed95ac01d9c41ef39d2036d57c525775a15dc672780a4c08aa02fc43

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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