Which versions of wn5ielist1a are malicious?

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

How do I remediate wn5ielist1a if I installed it?

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

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

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

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

Malicious package

wn5ielist1aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9408

Immediate action

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

gem uninstall wn5ielist1a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

820625d1770752732c09f2320df1be0f59b77492a1ef9456b9d4d25238b2e656

01c3729f15265df16c0f74859f3d2af7d25e50076a518bcc9454942f4768012f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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