Which versions of wprwn5xyz are malicious?

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

How do I remediate wprwn5xyz if I installed it?

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

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

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

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

Malicious package

wprwn5xyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9478

Immediate action

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

gem uninstall wprwn5xyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

1ba387caa2612e74effc70c12298422dddd9bd87887143eddd09c0712bed687b

3300b337123126a5b31d95616cdee94124a8dd20e62a42971b6484c335cd53a0

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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