Which versions of zwkopt20 are malicious?

The following RubyGems versions of zwkopt20 are flagged malicious: 0.0.3513. Treat any of these as compromised.

How do I remediate zwkopt20 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt20 (version 0.0.3513).

Malicious package

zwkopt20RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt20 (RubyGems)

MAL-2026-9884

Immediate action

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

gem uninstall zwkopt20

Malicious versions

1 flagged

0.0.3513

Indicators of compromise (SHA-256)

9d4a269d9e4f396108a3a25b744cf295789d1f72716eb06915cbab48183624ca

00d9c5029e3a46485e1a77d010786e1a4a78ff578238d5ee1848157638a88ffd

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04535RLUA-2026-10473

References

Credits

ReversingLabs · finder

Detect & block this

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