Which versions of zwkopt1 are malicious?

The following RubyGems versions of zwkopt1 are flagged malicious: 0.0.3488. Treat any of these as compromised.

How do I remediate zwkopt1 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt1 (version 0.0.3488).

Malicious package

zwkopt1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt1 (RubyGems)

MAL-2026-9872

Immediate action

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

gem uninstall zwkopt1

Malicious versions

1 flagged

0.0.3488

Indicators of compromise (SHA-256)

34e726ba3bbe5c19507a340ca1f9d80d75e731728ca8d4352e5ffcece470f73c

f83e0eee22edf08d67322b3a246292cc25149c9555572f1b1bb382c77178f620

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04523RLUA-2026-10461

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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