Which versions of wn5ielist2a are malicious?

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

How do I remediate wn5ielist2a if I installed it?

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

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

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

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

Malicious package

wn5ielist2aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9409

Immediate action

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

gem uninstall wn5ielist2a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0a78f4b7ca88bfba54c1f7ebb96c3d07408ad57cbb9b8e83d5c39e988e697c8e

2f760f7875f8a6a9c756ffb7bf81137269e6a66bfeff4ff7300263b7b149d37f

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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