Which versions of zwkopt16 are malicious?

The following RubyGems versions of zwkopt16 are flagged malicious: 0.0.3507. Treat any of these as compromised.

How do I remediate zwkopt16 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt16 (version 0.0.3507).

Malicious package

zwkopt16RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt16 (RubyGems)

MAL-2026-9879

Immediate action

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

gem uninstall zwkopt16

Malicious versions

1 flagged

0.0.3507

Indicators of compromise (SHA-256)

d38cce2c724efb3cc78739b36757026fa749dcc51fe551fc46246bc8cc6cb55e

54eb2aa969bfd8f6d347fe37044761b1e1d7445fa6bd3f6dde366a9795cbec84

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04530RLUA-2026-10468

References

Credits

ReversingLabs · finder

Detect & block this

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