Which versions of wmwk1nobab are malicious?

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

How do I remediate wmwk1nobab if I installed it?

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

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

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

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

Malicious package

wmwk1nobabRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9385

Immediate action

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

gem uninstall wmwk1nobab

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6276e1c70383d7c5a2243627e304b7aec514c147eee43488896abd8b23f895ad

299c42d9fc762780c72c8872fb3c9c6c8786f58da2dadc1024fb8ae20d96ae4a

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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