Which versions of wenc10010 are malicious?

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

How do I remediate wenc10010 if I installed it?

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

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

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

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

Malicious package

wenc10010RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9324

Immediate action

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

gem uninstall wenc10010

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7a9bd114cd52ae9d92e92fd1e574a8375c2acfa5a073dd3f4384682ac9d263a6

d7322ba1d625c2220968b7c003378da80ac14ad2b30f1db4dc2687add67aa296

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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