Which versions of zwkopt5 are malicious?

The following RubyGems versions of zwkopt5 are flagged malicious: 0.0.3493. Treat any of these as compromised.

How do I remediate zwkopt5 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt5 (version 0.0.3493).

Malicious package

zwkopt5RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt5 (RubyGems)

MAL-2026-9887

Immediate action

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

gem uninstall zwkopt5

Malicious versions

1 flagged

0.0.3493

Indicators of compromise (SHA-256)

16e35c2e93a55c1ab527a02d60b25a5ac65e06ba3300ca366cfa49e9d344661a

196cb8c96270389ec991221208310ad5d7493c07200fcd42006bc00bd0c0f341

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04538RLUA-2026-10476

References

Credits

ReversingLabs · finder

Detect & block this

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