Which versions of zwtenc1 are malicious?

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

How do I remediate zwtenc1 if I installed it?

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

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

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

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

Malicious package

zwtenc1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9906

Immediate action

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

gem uninstall zwtenc1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c46124509f74107b4e6e1deb6b634070d0749a92dbbe73af259a971f62c76be7

e2ecf5501fce2cb1eede0796e2d83ed96a8680a7eb0fe0b2e1a3c89fe1cd873e

Detection & response playbook

Malicious package

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

References

Credits

ReversingLabs · finder

Detect & block this

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