Which versions of zwknum2 are malicious?

The following RubyGems versions of zwknum2 are flagged malicious: 0.0.2768. Treat any of these as compromised.

How do I remediate zwknum2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwknum2 (version 0.0.2768).

Malicious package

zwknum2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwknum2 (RubyGems)

MAL-2026-9865

Immediate action

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

gem uninstall zwknum2

Malicious versions

1 flagged

0.0.2768

Indicators of compromise (SHA-256)

f6916cdc47bb55d0463d8e37ccf79b455d446377c114d530fc1d3bfe39b6a58f

05c3b5029d9718d67f09b56518bc2d972fd1bfa15be3ffa89ab770a1206af373

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04516RLUA-2026-10454

References

Credits

ReversingLabs · finder

Detect & block this

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