Which versions of wanproxyq are malicious?

The following RubyGems versions of wanproxyq are flagged malicious: 0.0.1, 0.0.2, 0.0.3, 0.0.4, 0.0.5. Treat any of these as compromised.

How do I remediate wanproxyq if I installed it?

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

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

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

Search your lockfiles and build artifacts for wanproxyq (5 malicious versions).

Malicious package

wanproxyqRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9302

Immediate action

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

gem uninstall wanproxyq

Malicious versions

5 flagged

0.0.10.0.20.0.30.0.40.0.5

Indicators of compromise (SHA-256)

a11acaae490b3dfeb596ecab8cef3e54ed4db296f734c2bf2e24abb939408d8e

a084436815313b7fb9622dfdc1d81aec9f8a771b3d9212168e0878c33c9a18d6

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for wanproxyq (5 malicious versions).
If you installed it — respond
Remove wanproxyq 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 wanproxyq 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. wanproxyq 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 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-03953RLUA-2026-09883

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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