Which versions of wmwk6nobab are malicious?

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

How do I remediate wmwk6nobab if I installed it?

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

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

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

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

Malicious package

wmwk6nobabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9405

Immediate action

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

gem uninstall wmwk6nobab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

5062a61cf96002d1f2892834c244b9c11713be0abfe2b14c4c7bdc75ddf5d06d

eeda4e46436257c77fe9357d7be07b9712f111ae92a1a8872fc6b276fcda97f5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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