A malicious user can craft an email "this is [abc.zip](http://very-bad-website)". Ok nothing new here.
But a non-malicious, who's emailing their mom: "I've attached abc.zip" (and put a abc.zip as attachment).
Here the problem here is a malicious other user has registered abc.zip to download a virus, and the mom's email client highlight abc.zip, and she clicks on it instead of the abc.zip attachment.
Your boss sends you this plaintext email:
Hi!
Please upload the photos as photos.zip to the company GDrive!
Thanks,
Boss
Your email client "helpfully" recognizes that "photos.zip" can be a TLD, so turns it automatically into a hyperlink. You click it because you think it's a link your boss intended to share with you, but you actually land on a site that pwns your browser with an exploit.There are 3 - yours, GP's, and GGP's.
None of the three seem like serious attack vectors to me.
I'm still having trouble coming up with a legitimate attack vector so I think there must not be one. I am ready to change my mind when I see one though.
Why not?
Hi! Please upload the photos as <a href="http://example.com/photos.zip">photos.zip</a> to the company GDrive!
So... what's new in your scenario?
What you think is an attachment from a trusted source is actually a link to the web.