Which versions of wenc10115 are malicious?

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

How do I remediate wenc10115 if I installed it?

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

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

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

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

Malicious package

wenc10115RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9325

Immediate action

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

gem uninstall wenc10115

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e5ef2749937ccbef3bf87ec0971b0a060f0d1bf03d6d63dcd012716cd3f1f8a0

29a43ff717f9702703279136d48e0dd49a2e06ed8603bad5e4d6a232e5b564e4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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