Which versions of zwtenc2 are malicious?

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

How do I remediate zwtenc2 if I installed it?

zwtenc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed zwtenc2 — how do I know if it already compromised me?

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

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

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

Malicious package

zwtenc2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

zwtenc2 is a confirmed malicious RubyGems package (MAL-2026-9907) that opens a backdoor for remote access (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in zwtenc2 (RubyGems)

MAL-2026-9907

Immediate action

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

gem uninstall zwtenc2

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

63cf4b5ce90a5dc246b78b6bdd17d4ced68a917f2e52963c32b907fc074820ae

8bfdae69663de5d896556405b1b907923f067dafa1bc000303e5b796711eecab

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for zwtenc2 (version 0.0.1).
If you installed it — respond
zwtenc2 establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If zwtenc2 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. zwtenc2 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-04558RLUA-2026-10496

References

Credits

ReversingLabs · finder

Detect & block this

O3 blocks zwtenc2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database