Which versions of zwkopt3 are malicious?

The following RubyGems versions of zwkopt3 are flagged malicious: 0.0.3491. Treat any of these as compromised.

How do I remediate zwkopt3 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt3 (version 0.0.3491).

Malicious package

zwkopt3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt3 (RubyGems)

MAL-2026-9885

Immediate action

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

gem uninstall zwkopt3

Malicious versions

1 flagged

0.0.3491

Indicators of compromise (SHA-256)

ef2cf288a101ea3708a75b466d31e6dedd104f5ac81bf80418bf1294ae9d3c15

bc802040cdd1287ddd1080a3312cbcc4f6486a0b3af7b0bb2ac1894fc1cff24c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04536RLUA-2026-10474

References

Credits

ReversingLabs · finder

Detect & block this

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