Which versions of wmwk4txtab are malicious?

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

How do I remediate wmwk4txtab if I installed it?

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

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

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

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

Malicious package

wmwk4txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9398

Immediate action

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

gem uninstall wmwk4txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9690be0eea5a49c854cc51ac6d493551c58de88dbea0847038004452b21740e9

af7a59068e44f199f405974629a043dc8f14c0317b54391fd13770679def8f62

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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