Which versions of wn5wknob2a are malicious?

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

How do I remediate wn5wknob2a if I installed it?

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

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

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

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

Malicious package

wn5wknob2aRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9412

Immediate action

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

gem uninstall wn5wknob2a

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

abc3e0682b9c55e1c0f52b45167acf20f706bf8ac4a0aff849a5c51b05abcc9c

0acc33815710df6ebdcdea06b24f35f681183b657e0ae90bf0bb27818e879b3d

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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