Which versions of wmwk3nobab are malicious?

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

How do I remediate wmwk3nobab if I installed it?

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

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

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

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

Malicious package

wmwk3nobabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9393

Immediate action

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

gem uninstall wmwk3nobab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

94f17824e14d4560eb7dab4a509ebdfc5114497170e13613f73705ad16d7eb52

507e3cc9ddebe0cfadf3ab039d98d99836f16b48e78300f5f648e96a2af65c0c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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