Which versions of zwknum4 are malicious?

The following RubyGems versions of zwknum4 are flagged malicious: 0.0.2770. Treat any of these as compromised.

How do I remediate zwknum4 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwknum4 (version 0.0.2770).

Malicious package

zwknum4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwknum4 (RubyGems)

MAL-2026-9867

Immediate action

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

gem uninstall zwknum4

Malicious versions

1 flagged

0.0.2770

Indicators of compromise (SHA-256)

c760e717ef5d4bfdc5cb9939d0cd8c63811715edeb527ff315bc045bc0173a53

22ee871b9cfadd70ac0b0e12b695034904089a5015080b13a04ac0f3fc912bd5

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04518RLUA-2026-10456

References

Credits

ReversingLabs · finder

Detect & block this

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