Which versions of wmwk3txtab are malicious?

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

How do I remediate wmwk3txtab if I installed it?

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

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

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

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

Malicious package

wmwk3txtabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9394

Immediate action

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

gem uninstall wmwk3txtab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

53e6027a9c105d28f50e13103c137c60c8e486a3bc70bf8437f0b3de08313c88

dece8809b1372fc5a79e0e003538a1a6dfaccd1bd9036b137c7bc87fee71632a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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