Which versions of wmwk3ab are malicious?

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

How do I remediate wmwk3ab if I installed it?

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

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

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

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

Malicious package

wmwk3abRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9391

Immediate action

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

gem uninstall wmwk3ab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fadeaa2f80446202066591a84f684737146c436337e38ad920436ec5211c14fd

08286d967b8f94357082ddccd5bfdb27ed7c1c5703363553db5e02180e6b809a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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