Which versions of zwknum5 are malicious?

The following RubyGems versions of zwknum5 are flagged malicious: 0.0.2771. Treat any of these as compromised.

How do I remediate zwknum5 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwknum5 (version 0.0.2771).

Malicious package

zwknum5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwknum5 (RubyGems)

MAL-2026-9868

Immediate action

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

gem uninstall zwknum5

Malicious versions

1 flagged

0.0.2771

Indicators of compromise (SHA-256)

fcc2e48a38c85a3d06860874b793e3ae13adce5eb9c6397bbfff619c4430687e

cc94105c94ee6f3a935b9f408793598c50be100c1fe121b48e2b39a7c107426f

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04519RLUA-2026-10457

References

Credits

ReversingLabs · finder

Detect & block this

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