Which versions of wmwk6ab are malicious?

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

How do I remediate wmwk6ab if I installed it?

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

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

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

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

Malicious package

wmwk6abRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9403

Immediate action

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

gem uninstall wmwk6ab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e7e5b11d9cf9fc9c1464a277105f26af65fa99aa5d6379a2238e5eefd30ca17f

b53ddbd10922c6160dc5a57ae37236268b42af6d44794a67796497412154747d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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