Which versions of zwknum0 are malicious?

The following RubyGems versions of zwknum0 are flagged malicious: 0.0.2765. Treat any of these as compromised.

How do I remediate zwknum0 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwknum0 (version 0.0.2765).

Malicious package

zwknum0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwknum0 (RubyGems)

MAL-2026-9863

Immediate action

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

gem uninstall zwknum0

Malicious versions

1 flagged

0.0.2765

Indicators of compromise (SHA-256)

9c2280ca3c65c6d664b525789f19e74612fd27d7bc9fc02cb4424292ddff3f36

ccc7c6c2c552f41891b581ddc45191de315cf024866c7ac56c7e80a567907c00

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04514RLUA-2026-10452

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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