Which versions of wmwk2txtab are malicious?

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

How do I remediate wmwk2txtab if I installed it?

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

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

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

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

Malicious package

wmwk2txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9390

Immediate action

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

gem uninstall wmwk2txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

bb1dd5f94460f15c0ddbfd983d13d7730434b27bc238280539fe15df1c5605f1

3338e451fe088ec511e5239c851eb6e7c61aebdfde657f68f0f1400d3d1d4aa6

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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