Which versions of zwknum3 are malicious?

The following RubyGems versions of zwknum3 are flagged malicious: 0.0.2769. Treat any of these as compromised.

How do I remediate zwknum3 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwknum3 (version 0.0.2769).

Malicious package

zwknum3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwknum3 (RubyGems)

MAL-2026-9866

Immediate action

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

gem uninstall zwknum3

Malicious versions

1 flagged

0.0.2769

Indicators of compromise (SHA-256)

6621b8c7a4cffa044f8b1deac059b0c7c5c93fd9c06ad14cf978e5e8a6576471

a3aa189e5c99e6f8a1e9ba625f8a59f3eb108380c530e1104387019582f82df6

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04517RLUA-2026-10455

References

Credits

ReversingLabs · finder

Detect & block this

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