Which versions of zwkopt19 are malicious?

The following RubyGems versions of zwkopt19 are flagged malicious: 0.0.3511. Treat any of these as compromised.

How do I remediate zwkopt19 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt19 (version 0.0.3511).

Malicious package

zwkopt19RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt19 (RubyGems)

MAL-2026-9882

Immediate action

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

gem uninstall zwkopt19

Malicious versions

1 flagged

0.0.3511

Indicators of compromise (SHA-256)

2369022ca9d657c6e7cfc6d4f854853e9671efc5d46a11759255876a5c91bd25

b0cbff2c89f27b119a390ea23889b9bbb4fdb55264ce368e75fe39ccff781528

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04533RLUA-2026-10471

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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