We have used TMSCryptography pack to produce a dll for generating and checking salted hashed passwords and it has been in use since July last year. Today out AV software ( and 28 others courtesy of VirusTotal.com) prevent it from loaded reporting that it contains a virus. Our secutiry team is now trying to tell me to remove the offending code but we haven't done much more than call a few functions provided by TMS Crypto. In the short term we have whitelisted the DLL in out own installations, but we have many external customers who might suffer the same problem and who might not be so willing to simpy whitelist our DLL
Has anyone else had a similar problem and if so what did you do to address it?