Which versions of zwkopt13 are malicious?

The following RubyGems versions of zwkopt13 are flagged malicious: 0.0.3503. Treat any of these as compromised.

How do I remediate zwkopt13 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt13 (version 0.0.3503).

Malicious package

zwkopt13RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt13 (RubyGems)

MAL-2026-9876

Immediate action

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

gem uninstall zwkopt13

Malicious versions

1 flagged

0.0.3503

Indicators of compromise (SHA-256)

3e66a17e684bf9fc3f36a1ea4692eea3f6fd3b54a43480a806f55ee1c30b6cb8

a9e9de41beb4167f5a68700b7f76922988f51d3040c347352abdbd7c4d3f9326

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04527RLUA-2026-10465

References

Credits

ReversingLabs · finder

Detect & block this

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