Which versions of zwxbcstan are malicious?

The following RubyGems versions of zwxbcstan are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate zwxbcstan if I installed it?

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

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

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

Search your lockfiles and build artifacts for zwxbcstan (version 0.0.1).

Malicious package

zwxbcstanRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

Malicious code in zwxbcstan (RubyGems)

MAL-2026-9932

Immediate action

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

gem uninstall zwxbcstan

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

44a6c0ccc3b1b2fc414d268de91da7c744db6286e2238ce6cd07638168bd05f8

c9e788edf03318e1e8eb4fc730512a914f1394a18d32cf846978ac0c6d32dd88

Detection & response playbook

Malicious package

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

Campaign

RLMA-2026-04583RLUA-2026-10521

References

Credits

ReversingLabs · finder

Detect & block this

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