Which versions of zwxbcsacre are malicious?

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

How do I remediate zwxbcsacre if I installed it?

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

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

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

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

Malicious package

zwxbcsacreRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zwxbcsacre is a confirmed malicious RubyGems package (MAL-2026-9931) 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 zwxbcsacre (RubyGems)

MAL-2026-9931

Immediate action

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

gem uninstall zwxbcsacre

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1ab9a59eaf2b4abd4a336b566ab40a84444152ca5e2ce3ec1dedca7dd10e5dff

eb8f98d70529d380f9af4a684da716905af86fac9ab4882a7d69b557c9790dfc

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for zwxbcsacre (version 0.0.1).
If you installed it — respond
Remove zwxbcsacre 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 zwxbcsacre 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. zwxbcsacre 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-04582RLUA-2026-10520

References

Credits

ReversingLabs · finder

Detect & block this

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