Hi, 1. As I understood your website and domain registration is brand new -- For obvious reasons a brand new website that hosts only an executable to be downloaded has a potential risk (meaning lots of malware authors are doing the same, so you might have a characteristic similar to this). 2. Could be that as a registrant you hide your name and address, phone number etc, which can add up to the bad reputation 3. Not sure where are you hosting that website but some web hosting services has less good reputations than other (usually cheap/free has less as that are more likely to be abused by malicious purposes) 4. Maybe your IP address or geographical location also in a range or location which has less reputation. 5. Now you download an executable which is I suppose not signed digitally with Verisign for example, so this may not help on And then possibly all or many of these combinations leads security companies to say your application is untrusted and could potentially be a malicious app. What I would do is to try to help on as many of these points as possible (get your app signed, make sure it is hosted on a trusted service and location, update whois information if possible). And of course you could report the False Positive to Google Safe Browsing service and to Avast too. 6. Oh, and of course check your website whenever is compromised by an attacker, apply security patches and remove malicious content that was injected by the attacker if there is any... Tamas On 21 June 2012 07:55, V G wrote: > Hi all, > > I am designing a system for a professor I am working for. One of the > components involves a Windows application that I've created and packaged > into a nice little installer (via NSIS). > > 1. I created a website (with my own domain) that is being used to host th= e > download for the installer file (via direct HTTP download). The problem i= s, > Google Chrome and Avast antivirus warns of it potentially being "malware" > because it's "not a commonly downloaded file". This will be quite a bit o= f > nuisance since the file is to be distributed internally to his team. > > 2. The program checks for updates and self updates. Avast also creates an > annoying warning that this could be malware. Any way to get around this? > > Is there a way to get Chrome and Avast to treat the file normally without > making users change their settings? Perhaps using a php redirect for the > download? If I host the file on a file sharing site, the warning isn't > shown. > -- > http://www.piclist.com PIC/SX FAQ & list archive > View/change your membership options at > http://mailman.mit.edu/mailman/listinfo/piclist > --=20 int main() { char *a,*s,*q; printf(s=3D"int main() { char *a,*s,*q; printf(s=3D%s%s%s, q=3D%s%s%s%s,s,q,q,a=3D%s%s%s%s,q,q,q,a,a,q); }", q=3D"\"",s,q,q,a=3D"\\",q,q,q,a,a,q); } --=20 http://www.piclist.com PIC/SX FAQ & list archive View/change your membership options at http://mailman.mit.edu/mailman/listinfo/piclist .