Which versions of wtenc1 are malicious?

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

How do I remediate wtenc1 if I installed it?

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

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

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

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

Malicious package

wtenc1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9485

Immediate action

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

gem uninstall wtenc1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

48cacfcbb0317660d6b58fef9594ae2619e26c379aa3ce85a71ac4f1ddf6d678

63e151e9a648707c0a502625cc3f9379f99a0be0aa87c77265a95ec64991e356

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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