Comment by kevincox
5 years ago
https://developers.google.com/safe-browsing/v4/update-api#ch...
TL;DR is you download a chunk of SHA-256 hashes and check if the hash for your URL is there. There is of course the chance of collision but that is minuscule.
Oh I know that's how that works, I meant, does Google transmit back the URLs once it does get a hit, to protect others from downloading that file?
Why would it need to do that? To protect others from the same url, the same hash checking method should work.
The blacklisted URL in this case is found in a downloaded file from a S3 bucket.
Other people downloading the same file would get the same "protection", but in this case this goes a step further:
The S3 bucket itself gets then blacklisted. As it was a private bucket, one of the ways this could happen is that once chrome found the blacklisted URL, it sent back to Google the url (s3 bucket) where the file with the blacklisted URL was found.