Which versions of wprwn6xyz are malicious?

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

How do I remediate wprwn6xyz if I installed it?

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

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

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

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

Malicious package

wprwn6xyzRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9480

Immediate action

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

gem uninstall wprwn6xyz

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

136d6d8534c10d074acd04cdf696c56c8a9987bc0b86c3cb3ccda9d2f63d3550

01120a6a3ca6b0607a2fbaff1ece6971c0a95f52a072d0b20f8e20656e9b7080

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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