Which versions of zwknum6 are malicious?

The following RubyGems versions of zwknum6 are flagged malicious: 0.0.2773. Treat any of these as compromised.

How do I remediate zwknum6 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwknum6 (version 0.0.2773).

Malicious package

zwknum6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zwknum6 is a confirmed malicious RubyGems package (MAL-2026-9869) that executes malicious code on install (malicious version 0.0.2773). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zwknum6 (RubyGems)

MAL-2026-9869

Immediate action

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

gem uninstall zwknum6

Malicious versions

1 flagged

0.0.2773

Indicators of compromise (SHA-256)

8e9842539751e0512758b5f354cb5956b6bbba9522c6ab62418ffd58da44eef7

63f315bb9d1d1bd96c004f23a0699067693c2c4031770fb46eaa3ea508377f1d

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zwknum6 (version 0.0.2773).
If you installed it — respond
Remove zwknum6 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 zwknum6 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. zwknum6 on RubyGems has been identified as a malicious package (version 0.0.2773 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-04520RLUA-2026-10458

References

Credits

ReversingLabs · finder

Detect & block this

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