Which versions of wtenc3 are malicious?

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

How do I remediate wtenc3 if I installed it?

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

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

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

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

Malicious package

wtenc3RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9487

Immediate action

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

gem uninstall wtenc3

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

b026669505eff027ba1230bfed5ceb4fa5c62920ad9a87fe6702d13bf7a5433c

f6820b2361d31621001634e9935d80a67f817a6f47c35e219c9c9bee5df1577c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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