Which versions of wandproxy1 are malicious?

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

How do I remediate wandproxy1 if I installed it?

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

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

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

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

Malicious package

wandproxy1RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9239

Immediate action

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

gem uninstall wandproxy1

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

0257baad12d4cd2f8f5bc3835cb9ead3104214f190636b7e4d7cdbd8b547284f

3de32c5ece86a56ca468941a6a9c5100d15501a5709d5ce50296fbc6cde8d48c

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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