I built an application with .NET 2003 some time ago, and today as I was scanning my PC with a-squared Free, it detected the following Trojan in my setup.exe (Used Visual Studio builder to create it):
Trojan-Dropper.Win32.Joiner.dp
How is this possible? The only file it is found is in that setup.exe....is there some code that gets detected as a trojan (the software is legit, it does stuff to XML files only
) and can I safely ignore this? It was built on another machine which was protected by Enterprise security and I just backed it up on my local machine.
Speaking of local machine, it has a Trojan in one of the Visual Studio library files, which was caught months ago by AVG - but I did not use this machine to build or even read the project in the setup.exe....so yeah, can I ignore this?
Trojan-Dropper.Win32.Joiner.dp
How is this possible? The only file it is found is in that setup.exe....is there some code that gets detected as a trojan (the software is legit, it does stuff to XML files only
) and can I safely ignore this? It was built on another machine which was protected by Enterprise security and I just backed it up on my local machine.Speaking of local machine, it has a Trojan in one of the Visual Studio library files, which was caught months ago by AVG - but I did not use this machine to build or even read the project in the setup.exe....so yeah, can I ignore this?
