Which versions of wnumghplcqou are malicious?

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

How do I remediate wnumghplcqou if I installed it?

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

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

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

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

Malicious package

wnumghplcqouRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9421

Immediate action

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

gem uninstall wnumghplcqou

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

93064b4cefd1b5ff8c8ae6beb16294e0d1caf2f0dae6ad6666fc7d12c5559185

efeb30bab1ca9de7621029b79f98397afc2a7cce10363f7ccbeedd3284aa1fa7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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