Which versions of wprwn2accxyz are malicious?

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

How do I remediate wprwn2accxyz if I installed it?

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

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

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

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

Malicious package

wprwn2accxyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9471

Immediate action

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

gem uninstall wprwn2accxyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

511d5b5271095add668c597ccd05b32595424b9a9ab8eeabfe4fc192581fde83

fa9f5d314c67461ce816ae34e8a8e366bff154452a2e182f11ae944843c11ed7

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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