Which versions of wanproxy2 are malicious?

The following RubyGems versions of wanproxy2 are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, 0.0.9, 0.0.10, 0.0.11. Treat any of these as compromised.

How do I remediate wanproxy2 if I installed it?

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

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

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

Search your lockfiles and build artifacts for wanproxy2 (11 malicious versions).

Malicious package

wanproxy2RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

wanproxy2 is a confirmed malicious RubyGems package (MAL-2026-9301) that executes malicious code on install (malicious versions 0.0.1, 0.0.2, 0.0.3…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in wanproxy2 (RubyGems)

MAL-2026-9301

Immediate action

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

gem uninstall wanproxy2

Malicious versions

11 flagged

0.0.10.0.20.0.30.0.40.0.50.0.60.0.70.0.80.0.90.0.100.0.11

Indicators of compromise (SHA-256)

e0c731f4fc38ece44baf8789f0a55ab1bf730cb9141890ed8878df2d95aa3565

f51862d3e2740b5bb6f2d05cf8e695e02b33dd9abddd51e72ac2b53ad5829693

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for wanproxy2 (11 malicious versions).
If you installed it — respond
Remove wanproxy2 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 wanproxy2 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. wanproxy2 on RubyGems has been identified as a malicious package (versions 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5, 0.0.6, 0.0.7, 0.0.8, and 3 more flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03952RLUA-2026-09882

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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