Which versions of zwkact4 are malicious?

The following RubyGems versions of zwkact4 are flagged malicious: 0.0.3289. Treat any of these as compromised.

How do I remediate zwkact4 if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwkact4 (version 0.0.3289).

Malicious package

zwkact4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwkact4 (RubyGems)

MAL-2026-9858

Immediate action

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

gem uninstall zwkact4

Malicious versions

1 flagged

0.0.3289

Indicators of compromise (SHA-256)

321b054518c294894c8b90aa7ad39b9cc0e56592d255f43d57c98e3102fe8e15

a177fa9cbfa62d4713394cccf74b3454347559b8ee49d51242cdcffca57aa829

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04509RLUA-2026-10447

References

Credits

ReversingLabs · finder

Detect & block this

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