Which versions of zwkopt6 are malicious?

The following RubyGems versions of zwkopt6 are flagged malicious: 0.0.3494. Treat any of these as compromised.

How do I remediate zwkopt6 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt6 (version 0.0.3494).

Malicious package

zwkopt6RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt6 (RubyGems)

MAL-2026-9888

Immediate action

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

gem uninstall zwkopt6

Malicious versions

1 flagged

0.0.3494

Indicators of compromise (SHA-256)

9c85bc82b731dbbb289868ce94ebe91bba43426436e3a9f07141524245656862

19191681df55202ade08fcd62746187650fbef478b6ee0c2ade6f0f16fd2894c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04539RLUA-2026-10477

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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