Which versions of wnekmzzveqou are malicious?

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

How do I remediate wnekmzzveqou if I installed it?

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

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

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

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

Malicious package

wnekmzzveqouRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9415

Immediate action

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

gem uninstall wnekmzzveqou

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

3069b5882489cd84c9f50a17dd3c0b85655e207bad710628de5d8b2d6cc8d287

66a21f7b2d0cc972d09e4f61cf9199b590fdff31cfdf54fb355a82286449d0c5

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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