Which versions of zwkopt4 are malicious?

The following RubyGems versions of zwkopt4 are flagged malicious: 0.0.3492. Treat any of these as compromised.

How do I remediate zwkopt4 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkopt4 (version 0.0.3492).

Malicious package

zwkopt4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkopt4 (RubyGems)

MAL-2026-9886

Immediate action

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

gem uninstall zwkopt4

Malicious versions

1 flagged

0.0.3492

Indicators of compromise (SHA-256)

8840f392193857c14db17db30958c2a4a0b76e84b73d9a44e268d649ee8c6b5a

a3cd1abba079bbcd573f507e216b2b04fbdb42996bdde6f560dac7e7e46a6c7c

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04537RLUA-2026-10475

References

Credits

ReversingLabs · finder

Detect & block this

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