Which versions of wprwn4accxyz are malicious?

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

How do I remediate wprwn4accxyz if I installed it?

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

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

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

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

Malicious package

wprwn4accxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9475

Immediate action

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

gem uninstall wprwn4accxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

6fc9cd4b25fb29963df04d0b116521a7afd88ba90bb666da65c1d6c5c81352d0

9237a8a302cb537025d9bbdc4692ddcad831d49d7a3d5b3579255c85a9de5c39

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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