Which versions of zwkopt15 are malicious?

The following RubyGems versions of zwkopt15 are flagged malicious: 0.0.3506. Treat any of these as compromised.

How do I remediate zwkopt15 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt15 (version 0.0.3506).

Malicious package

zwkopt15RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt15 (RubyGems)

MAL-2026-9878

Immediate action

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

gem uninstall zwkopt15

Malicious versions

1 flagged

0.0.3506

Indicators of compromise (SHA-256)

6dfcecfcbff4c362c1581aeec7f6edb7482c07f90fb7fdbbbb28114b3f41cd8a

ee2b878072ed273db2a02592073273eff09da681a9ff8eb8184617cdad7e8d57

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04529RLUA-2026-10467

References

Credits

ReversingLabs · finder

Detect & block this

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