Which versions of wprwn3accxyz are malicious?

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

How do I remediate wprwn3accxyz if I installed it?

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

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

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

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

Malicious package

wprwn3accxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9473

Immediate action

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

gem uninstall wprwn3accxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

99f289a50babfdae9148f3fc6bdb22020343d2ba5ae2aa115114553745a6e631

4bafa1393d87feba4dd35e6d83d8dcd4e8530d9fd78e498f0bb5d6c34a7491e7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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