DependencyWatch.io
FeedSolutionsSubmitScan your lockfile
Highcrates.io2 affected versions

lsh

lsh has 2 versions on crates.io flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with cargo tree -i lsh.

  • lsh@99.1.0
  • lsh@99.0.1

The incident that flagged it

High

crates.io dependency-confusion burst - 9 Rust crates targeting AWS, Mysten Labs, Replit, Proton, plus 4 generic-name typosquats, all flagged by OpenSSF Package Analysis on 2026-07-18

On 2026-07-18 the OpenSSF Package Analysis project flagged 9 Rust crates as malware - all yanked from crates.io within hours and mirrored into the GitHub Advisory Database as CWE-506 records. The 99.x.x version pins on mysten-metrics, amzn-codewhisperer-streaming-client, amzn-consolas-client, replit_ruspty, semantic-search-client, supertag, proton-pfff, and lsh are classic dep-confusion telltales. Every crate communicates with an attacker-controlled domain and executes commands on install.

Versions named here: 99.0.1, 99.1.0

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

  1. 1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
  2. 2.Pin to a version not listed above, then reinstall from a clean lockfile.
  3. 3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
  4. 4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

lsh is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. We don't parse crates.io manifests yet, but the incident write-ups list every affected package.

Browse the incident feed All flagged crates.io packages

Other packages in the same incident

If lsh is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.