Which versions of wnuqwugrxxae are malicious?

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

How do I remediate wnuqwugrxxae if I installed it?

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

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

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

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

Malicious package

wnuqwugrxxaeRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9422

Immediate action

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

gem uninstall wnuqwugrxxae

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

744f130b9999f4f2fdc553fd8a308cb6dff3af05289bbae4c254d0cf4697bdad

64d161f9d06b46e7c40ad9be1413e1af547a18dd796e88e57f8802a57902115b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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