Which versions of wmwk2bothab are malicious?

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

How do I remediate wmwk2bothab if I installed it?

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

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

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

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

Malicious package

wmwk2bothabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9388

Immediate action

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

gem uninstall wmwk2bothab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

9ebfa89ee8bc580a12f43eb2c3eee78de406a0fae0378ea4819d3e7ec5908710

3f441eb1c10c6353759144b3cb35b209a5dd60d21ddf56024537f6da32848c6e

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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