Which versions of wwandsvn are malicious?

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

How do I remediate wwandsvn if I installed it?

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

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

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

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

Malicious package

wwandsvnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9495

Immediate action

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

gem uninstall wwandsvn

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

16b2d14d9c655de5dcccf143acf1bddc415133e260dcd5506f7dded548179dc1

397eea888189113ae690e07f631e2d2a08479c5f97c382c48a42c5ed6d3561e4

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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