Which versions of wprwn3xyz are malicious?

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

How do I remediate wprwn3xyz if I installed it?

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

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

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

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

Malicious package

wprwn3xyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9474

Immediate action

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

gem uninstall wprwn3xyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

cba0d3a18fb09f008f33027058a69d8153e91ffb546b9f7a46b20966ce1657b1

7e719ab8c5f8047383a9e2bff2ae1b855452032d52aaeb357dd9609ce1602ff2

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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