Which versions of zwtenc0 are malicious?

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

How do I remediate zwtenc0 if I installed it?

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

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

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

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

Malicious package

zwtenc0RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9905

Immediate action

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

gem uninstall zwtenc0

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

98e5c78628fe2101ff64bb69be12f1ad80f757c618927bcbbfcc60995532e02e

74e9e10bdf126e799c6578be21a8ab165165b3d60b7b584ad3ee85be8de4223e

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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