Which versions of wmwk2nobab are malicious?

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

How do I remediate wmwk2nobab if I installed it?

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

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

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

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

Malicious package

wmwk2nobabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9389

Immediate action

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

gem uninstall wmwk2nobab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b1bf2ad850958a695f1d0382c54f93b6996b7c0bec61fa91972a5d693503bf77

9811b98ce7764854a62e37405814aa36d32b016c54e0f0f148bf0fa23f03cf8d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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