# supertag - compromised crates.io versions

> supertag on crates.io has 1 version flagged in 1 tracked supply-chain incident. Only the exact versions listed below were named by the source advisories. supertag is a dependency-confusion probe: a public package squatting an internal-looking name at a sentinel version. It never had a legitimate public version. A hit means a resolver on that machine reached the public registry for an internal name, which is itself worth fixing.

- Package: supertag
- Ecosystem: crates.io
- Highest severity: high
- Kind: Dependency confusion
- Compromised versions: 99.1.1
- Check what you have installed: `cargo tree -i supertag`

## The incident that flagged it

| Date | Severity | Kind | Incident | Versions named |
|---|---|---|---|---|
| 2026-07-18 | high | Dependency confusion | [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](https://dependencywatch.io/incident/crates-2026-07-18-openssf-typosquat-burst) | 99.1.1 |

## What to do if you installed one of these

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

## Check your whole project

We don't parse crates.io manifests yet, but the incident write-ups list every affected package. Incident feed: https://dependencywatch.io/feed

All flagged crates.io packages: https://dependencywatch.io/package/crates

## Other packages in the same incident

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

- [amzn-codewhisperer-streaming-client](https://dependencywatch.io/package/crates/amzn-codewhisperer-streaming-client) (crates.io)
- [amzn-consolas-client](https://dependencywatch.io/package/crates/amzn-consolas-client) (crates.io)
- [littest](https://dependencywatch.io/package/crates/littest) (crates.io)
- [lsh](https://dependencywatch.io/package/crates/lsh) (crates.io)
- [mysten-metrics](https://dependencywatch.io/package/crates/mysten-metrics) (crates.io)
- [proton-pfff](https://dependencywatch.io/package/crates/proton-pfff) (crates.io)
- [replit_ruspty](https://dependencywatch.io/package/crates/replit_ruspty) (crates.io)
- [semantic-search-client](https://dependencywatch.io/package/crates/semantic-search-client) (crates.io)

Full incident: https://dependencywatch.io/incident/crates-2026-07-18-openssf-typosquat-burst

## Sourcing

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. Corrections: https://dependencywatch.io/submit

---

Canonical page: https://dependencywatch.io/package/crates/supertag
Markdown version: https://dependencywatch.io/package/crates/supertag.md
Site index for agents: https://dependencywatch.io/llms.txt
DependencyWatch.io is operated by Precursor Security (https://precursorsecurity.com).