Which versions of zwknum1 are malicious?

The following RubyGems versions of zwknum1 are flagged malicious: 0.0.2766. Treat any of these as compromised.

How do I remediate zwknum1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwknum1 (version 0.0.2766).

Malicious package

zwknum1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwknum1 (RubyGems)

MAL-2026-9864

Immediate action

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

gem uninstall zwknum1

Malicious versions

1 flagged

0.0.2766

Indicators of compromise (SHA-256)

68dfb326c849dace1a88a7b0d9839bddb0fad461d1f3805301ff6feadc440fb4

8a9132789723f17dd9b093255766c669ed61058c0680581a66c2f4139aca8e32

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04515RLUA-2026-10453

References

Credits

ReversingLabs · finder

Detect & block this

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