Which versions of zwkopt18 are malicious?

The following RubyGems versions of zwkopt18 are flagged malicious: 0.0.3509. Treat any of these as compromised.

How do I remediate zwkopt18 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt18 (version 0.0.3509).

Malicious package

zwkopt18RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt18 (RubyGems)

MAL-2026-9881

Immediate action

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

gem uninstall zwkopt18

Malicious versions

1 flagged

0.0.3509

Indicators of compromise (SHA-256)

93c05d12f5bce135327825dd37d0136a51a2e0bda5aa4e5c9c03a669561a9761

3393818cfb2b75f7a4a42721ba58aa12c3a93dad3a1e23a800576a0058695056

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04532RLUA-2026-10470

References

Credits

ReversingLabs · finder

Detect & block this

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