Which versions of zwkopt14 are malicious?

The following RubyGems versions of zwkopt14 are flagged malicious: 0.0.3504. Treat any of these as compromised.

How do I remediate zwkopt14 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt14 (version 0.0.3504).

Malicious package

zwkopt14RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt14 (RubyGems)

MAL-2026-9877

Immediate action

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

gem uninstall zwkopt14

Malicious versions

1 flagged

0.0.3504

Indicators of compromise (SHA-256)

47cf40c9bb92d2c737cc2d317792e974b98eb04b85b8f7f3575545351dfa2e99

49a423892ee94fc9d767039a96d8798cb2a916b391815590154eb0962437dffe

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04528RLUA-2026-10466

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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