Which versions of wnizcisqddnw are malicious?

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

How do I remediate wnizcisqddnw if I installed it?

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

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

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

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

Malicious package

wnizcisqddnwRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9417

Immediate action

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

gem uninstall wnizcisqddnw

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cbbcac6b89b2f674dffc957634f825a1db085d86caea2e3fba39e74068b50ac1

36f1bb2db3de916530320690bd533b93441bbfd4458b887c02e956bc981d1b42

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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