Trojan Virus and Visual Basic Executable file

November 4, 2010 at 17:19:12
Specs: Windows 7
I made a program in Visual Basic using command buttons, image boxes, lines and labels. This was a very simple program. I needed to give the program as a project to my professeur. However she does not have visual basic on her computer so I had to make it an executable file. It was a simple process that I have done a thousand times. However this time when it completed my computer read it as a trojan virus. When I tried to click on it said I did not have the necessary premission to do it.

I have tried to remake the program on the same computer and a different computer. It has done the same thing every time I have tried. Does anyone know the cause and more importantly how to get around it.

If this helps I have AVG security system for my virus protection.

See More: Trojan Virus and Visual Basic Executable file

Report •

November 5, 2010 at 05:18:12
Assuming you don't have a virus that's infecting these complied executables, then chances are it's a false positive. Either change your program sufficiently to avoid detection, or work with AVG to remove the false positive. (Read: Disable AVG when running your program.)

How To Ask Questions The Smart Way

Report •

November 5, 2010 at 11:32:03
I ran a virus check and there are not any on my computer. How would a virus get just into the executables?

I am not sure how I would alter the files. All the program is is just viewing pictures and their labels at diffent times. How would this make a false positive.

I thank you for your help but do you have any ideas what would caus AVG to read it as a virus, cause the false positive.

Report •

February 14, 2011 at 01:43:26
Can we say, Root Kit anyone? Yes. It's possible that you have something binding to your generated exe's (or at the very least, a hidden system process which checks and binds itself to 'clean' exe files the moment one is created).

What I would suggest is this: Try creating your exe from a virtual machine with a clean copy of windows and avg freshly installed (if you don't have vmware or can't obtain it, you can download a copy of VirtualBox which is freeware, and install it onto that.

Even if your primary system is infected, you will be able to isolate code generation virtually to see if you have the same issue that was seen on your physical machine.

If you still get the same result, then it's possible you have a false-positive from AVG as reported above. If not, I would copy off your data immediately and back up anything important you have (and I do mean everything that you don't want to lose) to an external drive, format your system, and start over with a fresh copy of windows. Use virtualbox as your virtual VB sandbox, and general program barrier to protect you from now on.

There are a LOT of things that get past AVG, Norton, Kapersky, F-PROT, and all your major virus providers and several methods to do it. I know because I used to write code like this to attack my own systems and reverse-engineer other's executables and dll's to see how things worked from virtual machines so I could stay safe. A virtual machine will keep you safe from most every virus threat (except code execution via host source attacks/hypervisor exploits).

Be certain to verify that your version of Visual Basic is clean, too. If the compiler you have for Visual Basic has been compromised, then every EXE you create will be infected with their code even if you only intended to produce an exe with your own. Stay safe. -James

Report •

Related Solutions

Ask Question