Which versions of wprwn2xyz are malicious?

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

How do I remediate wprwn2xyz if I installed it?

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

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

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

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

Malicious package

wprwn2xyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9472

Immediate action

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

gem uninstall wprwn2xyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0c46966068d4e6baeaae0d955ba7962a3c8993dc6628c946679f9f72cb5d8e6c

db176e4932d21c2de308047f37943e845d8fad4f3e0ec50b8a564128a97e856b

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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