Which versions of wn5wknotxt1 are malicious?

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

How do I remediate wn5wknotxt1 if I installed it?

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

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

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

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

Malicious package

wn5wknotxt1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9413

Immediate action

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

gem uninstall wn5wknotxt1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f72eab4eb1dc18014500367440fdc9ff10b5748be04a57bf7a9e575c02277f11

1257ff351bbc28d245dbf36f84f491a53da76048f56fb38c691cd1a7dcab276d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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