What does the lsh malware do?

The OpenSSF Package Analysis project identified 'lsh' @ 99.0.1 (crates.io) as malicious. It is considered malicious because: - The package communicates with a domain associated with malicious activity. - The package executes one or more commands associated with malicious behavior.

Which versions of lsh are malicious?

The following crates.io versions of lsh are flagged malicious: 99.0.1, 99.1.0. Treat any of these as compromised.

How do I remediate lsh if I installed it?

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

If lsh 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.

How do I find lsh across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for lsh (2 malicious versions).

Malicious package

lshcrates.io

Advisory published Apr 28, 2026Updated Jul 23, 2026

lsh is a confirmed malicious crates.io package (MAL-2026-3126) that executes malicious code on install (malicious versions 99.0.1, 99.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in lsh (crates.io)

MAL-2026-3126

Immediate action

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

remove lsh

What this malware does

The OpenSSF Package Analysis project identified 'lsh' @ 99.0.1 (crates.io) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.
The package executes one or more commands associated with malicious behavior.

Malicious versions

2 flagged

99.0.199.1.0

Indicators of compromise (SHA-256)

8cd6cecd3051e3998c5f96ec8dbe1bcfffc1ed7133d394a1779c8c1b0252c8c0

0d659fd33aac3eba6d4a9616642cd843d8cb7ae8a7433d94cad9dade68235d9e

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for lsh (2 malicious versions).
If you installed it — respond
Remove lsh 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 lsh 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. lsh on crates.io has been identified as a malicious package (versions 99.0.1, 99.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Credits

OpenSSF: Package Analysis · finder

Detect & block this

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