Which versions of wenc9927 are malicious?

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

How do I remediate wenc9927 if I installed it?

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

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

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

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

Malicious package

wenc9927RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9327

Immediate action

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

gem uninstall wenc9927

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

8391c85e67dda4b876c90cd8f6e2d115523c48c19c310851acf67c14bd544491

20e7886f9595838f62328c6f6f2ea56f4e348a901049a34ae25b0fbea876a9d9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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