Which versions of wlamsvn are malicious?

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

How do I remediate wlamsvn if I installed it?

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

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

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

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

Malicious package

wlamsvnRubyGems

Advisory published Jul 7, 2026Updated Sep 24, 2026

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

MAL-2026-9373

Immediate action

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

gem uninstall wlamsvn

Malicious versions

1 flagged

0.0.1

Indicators of compromise (SHA-256)

005cee5ac7ade1f1eb71f72a70764cdd0bb25a318f4f8c6ed19e9c93dea673bc

df3a0dc32871a5451d3170626d8acc6c646253fc673cf08c19b6c4ab2269a566

Detection & response playbook

Malicious package

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

References

github.com

Credits

ReversingLabs · finder

Detect & block this

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