Which versions of wandproxy4 are malicious?

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

How do I remediate wandproxy4 if I installed it?

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

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

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

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

Malicious package

wandproxy4RubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9242

Immediate action

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

gem uninstall wandproxy4

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

e014b8a7a5fa6a090f0dfd459aff4173e751544a289b6a6cdd53398115e1d958

84722e395e0f95baa00216c11a4244412c8935d2089eb399f7dfc196d01fd1f4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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