Which versions of zswacta23998 are malicious?

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

How do I remediate zswacta23998 if I installed it?

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

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

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

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

Malicious package

zswacta23998RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9795

Immediate action

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

gem uninstall zswacta23998

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

121060bbcbf48f6cde727473a5d49a13d8301e34dd19975d53987ef0a04ad8c7

19bde56b3e6bc4104288d2628b51243417b53a0c9ace8bd723e2e293504f166b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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