Which versions of wmwk3bothab are malicious?

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

How do I remediate wmwk3bothab if I installed it?

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

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

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

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

Malicious package

wmwk3bothabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9392

Immediate action

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

gem uninstall wmwk3bothab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8ed1ae6b3fd49381a6e1e02e01b4812e7a30ffe0d41d9f1bef171d46cee3f4b5

cfbd341d40e9e2cfd1944d9a7d73de41692ce8a78408e40e22c44f479e3308e5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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