Which versions of wmwk1ab are malicious?

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

How do I remediate wmwk1ab if I installed it?

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

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

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

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

Malicious package

wmwk1abRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9383

Immediate action

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

gem uninstall wmwk1ab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

d70b6bcc94a659b7a277fca6094ccc5f45ddcc6ca936760284ee9383a258059d

927153ee095e7a0a4d3326e5161ca2fa9433b853a9e75bf05e93fe13827ca0bc

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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