Which versions of wprox-c217-2bzr are malicious?

The following RubyGems versions of wprox-c217-2bzr are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate wprox-c217-2bzr if I installed it?

wprox-c217-2bzr establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

I already installed wprox-c217-2bzr — how do I know if it already compromised me?

If wprox-c217-2bzr 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 wprox-c217-2bzr part of a known attack campaign?

Yes — wprox-c217-2bzr is associated with the RLMA-2026-04108, RLUA-2026-10040 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 wprox-c217-2bzr across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for wprox-c217-2bzr (version 0.0.1).

Malicious package

wprox-c217-2bzrRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

wprox-c217-2bzr is a confirmed malicious RubyGems package (MAL-2026-9457) that opens a backdoor for remote access (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wprox-c217-2bzr (RubyGems)

MAL-2026-9457

Immediate action

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

gem uninstall wprox-c217-2bzr

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

c0a0a34b575429cb0842cb6e15af49a83e1fd91567c90415af53ffbf90e40322

4f6feb63e0f782e18c3aea4e848e0385b27e09edad57e77ac262ef6070215aa3

Detection & response playbook

Backdoor / remote access

Find it
Search your lockfiles and build artifacts for wprox-c217-2bzr (version 0.0.1).
If you installed it — respond
wprox-c217-2bzr establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If wprox-c217-2bzr 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. wprox-c217-2bzr 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-04108RLUA-2026-10040

References

github.com

Credits

ReversingLabs · finder

Detect & block this

O3 blocks wprox-c217-2bzr-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the C2 callback and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database