content: It's not even Chrome specifically doing this bullshit (bad enough on its own anyway, though); I had the same damn thing happen on a download that was quite clearly not malware (support forum even had a topic about it being erroneously flagged). It's Google's actual malware detection list doing this shit. Mozilla never did respond with anything in the topic more than a non-committal "Uh...We...Don't actually control that. So....Er...Maybe it might get fixed?" kind of reply, so I turned it right the fick off and just run regular virus scans.