Verifying backend files explains this verification test which appears to be detecting corrupted files. Language could be simpler, but Cryptographic hash function is sort of like a fingerprint of that file.
Duplicati database knows what it should be, but upon download the file does not give the answer.
If they are dblock files, that might not be noticed or cleared by database Recreate which uses dlist and dindex files ideally. The problem with bad dblock file is that you may have lost source file data.
What is the Storage Type of the destination? Any idea how reliable it is against corruption of files?
You might eventually decide to do a thorough files survey, for example using The TEST command.
As described by @ts678 this means that the remote file has been modified. This is usually a sign of damaged remote storage and will likely mean that parts of your backup cannot be restored.