Which versions of wmwk5nobab are malicious?

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

How do I remediate wmwk5nobab if I installed it?

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

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

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

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

Malicious package

wmwk5nobabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9401

Immediate action

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

gem uninstall wmwk5nobab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

a166f985c680b1f3420aff24b0a3897a9629025be0f789bee4a8e2c4b334537f

210f93a49f0983204a6e6b83b187eb4de512dbfad7c20879d645650e19c42d8d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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