Re:Phish-Friendly Domain Registry ".top" Put on Notice
by w-m on Wednesday July 24, 2024 @05:38PM
(#41062443)
My point was that the person fooled by https://foo.zip/ would have been also fooled by https://foo.com/bar.zip, so the existence .zip wouldn’t change much.
But now I’ve understood that the auto-linkification of a simple non-link mention like update.zip can be indeed dangerous.
Re:Phish-Friendly Domain Registry ".top" Put on Notice
by godzillabrennus on Thursday July 25, 2024 @01:11AM
(#41064925)
Imagine a URL like http://www.chase.com.auth.statement.zip
Average users would never suspect a thing.
Re:Phish-Friendly Domain Registry ".top" Put on Notice
by eli on Thursday July 25, 2024 @10:14AM
(#41068922)
I genuinely do not see how that is different than http://www.chase.com.auth.statement.com
Re:Phish-Friendly Domain Registry ".top" Put on Notice
by diggan on Thursday July 25, 2024 @10:51AM
(#41069395)
Turn of all of your developer knowledge for a minute.
You click on a link "very-trustworthy-ceo-information.zip" in a mail, since you want to download this very important information from your CEO. Sure, your browser pops up, but it does that all the time so who cares, and then there is a file "very-trustworthy-ceo-information.zip" in your downloads folder. Native Outlook might usually open it in a different way usually, but who cares? OWA - you won't notice a difference in the UI at all. But anyway, important CEO information. Open the zip, open the PDF, oops your workstation is compromised.
If we turn our technical knowledge back on, it's rather simple. A user was phished to open a link to "https://very-trustworthy-ceo-information.zip". This returned with a file download, obviously called "very-trustworthy-ceo-information.zip", containing whatever I want to contain based off of IPs and whatever I can stuff into the link in a hidden fashion the average user won't note.
A lot of people would not be able to distinguish between https://foo.zip answering with a binary content type and naming the file foo.zip through content disposition headers and foo.zip coming from a trusted source.
And honestly, I would personally have to double-check what's going on there if it happened to me.