There are ways to corrupt a file without messing with the hex content of the file
So if file 1 is a bitstring, you don't modify the bits to produce file 2, then file 2 has the same bitstring and will be processed the same as file 1.
You can never be certain wherever the damage was caused by bitrot or a person screwing with the file, but certain patterns are very unlikely to occur naturally so a reasonable guess is at least somewhat possible
Benjamin : Yes, sir.
Mr. McGuire : Are you listening?
Benjamin : Yes, I am.
Mr. McGuire : Metadata.
(also see https://en.wikipedia.org/wiki/Resource_fork)
"The Windows NT NTFS can support forks (and so can be a file server for Mac files), the native feature providing that support is called an alternate data stream."