# File Hashes

imphash, ssdeep, TLSH, and so forth: what survives a change, and what a match lets you claim.

Every scheme here gets quoted as if it identified a malware family. Most identify something narrower, and a couple identify something else. Each row says what the hash is computed over, because that predicts everything else about it.

## Before you read the table

- Exact hashes change if one byte changes. A match is not a judgment call.
- Similarity hashes are built to survive change, which is why a match is weaker evidence than it looks.

## Related

- [Decoder: Hash](https://www.cyberkit.win/tools/decoder/?tab=hash)
- [Decode Range: Hashes](https://www.cyberkit.win/drills/decode-range/?stage=hashes)
- [Pyramid of Pain](https://www.cyberkit.win/reference/pyramid-of-pain/)

Canonical: https://www.cyberkit.win/reference/file-hashes/

This is a static reference page. It does not collect anything.
