Which versions of wanqproxy are malicious?

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

How do I remediate wanqproxy if I installed it?

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

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

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

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

Malicious package

wanqproxyRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9303

Immediate action

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

gem uninstall wanqproxy

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

7fb9f8095917323d6ff6174999ce0988ac4a0e0934b0b1639329b3c74c738fd1

84eca38fe5558d6654b911b90e1eebc8a882590ff06831fff93b8bfc00cd2aaa

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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