Which versions of wn5agnotxt1 are malicious?

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

How do I remediate wn5agnotxt1 if I installed it?

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

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

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

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

Malicious package

wn5agnotxt1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9407

Immediate action

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

gem uninstall wn5agnotxt1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c9bbcd2abf46c49360a0209abc50cdf0fcd35f0450a6ddfa6a5e7d72afcae78c

59df20644a9bd3712a235405d9771e135026770681ad39a2edab0208f7d007fb

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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