Which versions of wmwk4nobab are malicious?

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

How do I remediate wmwk4nobab if I installed it?

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

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

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

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

Malicious package

wmwk4nobabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9397

Immediate action

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

gem uninstall wmwk4nobab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

716c78710fcba777d62216433daaacd5606e0caae3b4fbd6b7799e180c0a3020

71ae04b1a45db6dd7fc9f3027a54fa425a0d93d1f5d666c036fc67b2ea47c62d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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