Which versions of wprwn5accxyz are malicious?

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

How do I remediate wprwn5accxyz if I installed it?

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

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

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

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

Malicious package

wprwn5accxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9477

Immediate action

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

gem uninstall wprwn5accxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

317ee5c054a6596d10d3f15a489f9ecc93eea79887585c9ad5a8b225db8a3ae4

5c469d7c0bd89b5899474f3daf12aa566ade6df32b33f6a450153e77ddc318a9

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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