Which versions of wmwk2ab are malicious?

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

How do I remediate wmwk2ab if I installed it?

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

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

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

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

Malicious package

wmwk2abRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9387

Immediate action

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

gem uninstall wmwk2ab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1f607cec3dd0daaa68294773b61c64a3241212bba83b6d70fe1e7e236e574790

8934d10f0514c4a5efa892628518b82ef6270d1f9ee5914c37b805b69421cd73

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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