Which versions of wprwn4xyz are malicious?

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

How do I remediate wprwn4xyz if I installed it?

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

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

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

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

Malicious package

wprwn4xyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9476

Immediate action

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

gem uninstall wprwn4xyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

f0c24b732684f076f433c050e3c8edf17a22faf422230c6ad69aac1972a060fa

989913918df687c5315096c8be12474af4ded46ff459afd9d5da2aa69cfb30da

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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