Which versions of wmwk5txtab are malicious?

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

How do I remediate wmwk5txtab if I installed it?

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

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

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

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

Malicious package

wmwk5txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9402

Immediate action

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

gem uninstall wmwk5txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

4d5b57f521965d2c69cdb91071f1500c83cedd75d40a9acd38746a642ee609a4

8da983430f89d889d49fb159c10b666866b387c8c3533e14578d015d4db30000

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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