Which versions of wenc10385 are malicious?

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

How do I remediate wenc10385 if I installed it?

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

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

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

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

Malicious package

wenc10385RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9326

Immediate action

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

gem uninstall wenc10385

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

fee877971b46f9e5347398707127bab01695f8541ca05df4325aa9dd1288dd92

9bec3ea3859ae0e1360714d0d7d2db472e55ce995ee2afd5f84a321662df1e07

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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