Which versions of zwknum7 are malicious?

The following RubyGems versions of zwknum7 are flagged malicious: 0.0.2774. Treat any of these as compromised.

How do I remediate zwknum7 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwknum7 (version 0.0.2774).

Malicious package

zwknum7RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwknum7 (RubyGems)

MAL-2026-9870

Immediate action

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

gem uninstall zwknum7

Malicious versions

1 flagged

0.0.2774

Indicators of compromise (SHA-256)

fe165b2ab15b612902fec9953145e9c20bd657dd8a65761a574a3816fc51f28f

b308cd54716b4c3b10ebfe70b34759931aea723bb426e1e38e943f54305f3e91

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04521RLUA-2026-10459

References

Credits

ReversingLabs · finder

Detect & block this

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