Malwarebytes provides a trojan warning for basic C # "Hello World!" program

Question

Basically, I just ran a scan of my computer with Malwarebytes (updated the definitions before starting), and he said that my "helloworld" ", written in C #, has trojan .

I know this is a false positive since I only wrote the program 2-3 days ago and followed a small training site to make a program that I trust. I'm new to C #, but I don't see anything that could give a warning about the trojan.

The program manages the executable file, but is not the source file.

using System; namespace HelloWorldApplication { class HelloWorld { static void Main(string[] args) { Console.WriteLine("\n\tHello World!"); Console.WriteLine("This is my first C# program.\nI'm so proud of myself!"); Console.WriteLine("\tTeehee!"); } } } 

This is code written in Notepad ++ , and it is run from the command line ( Cygwin , in fact). Why does this mean it? Is this something that, as a novice C # programmer, should I know?

Answer 1

The problem may be that Trojan Backdoor.MSIL.PGen is usually called "hello.exe". The name of your executable file is presumably "hello.exe" or "helloworld.exe".

Just rename your project or change the output executable to something that does not contain “hi,” and it should stop detecting it.

This answer is somewhat speculative, but given the name of your project and the history of overly aggressive detection of this malware (see here ), this seems like a reasonable hit.

Answer 2

Baldrick's answer is most likely correct, but there is another possibility: there are viruses that look for random executable files in the system and modify them by inserting their own code into them (this is, in fact, the original definition of “ computer virus ”). When you find that an executable file that you know is trustworthy is reported as infected, you can deal with such a virus.

But if your antivirus does not report other executable files as the same virus, this is unlikely.

Answer 3

I just figured it out: change the "Guid" in AssemblyInfo.cs a bit, then try again.

It worked for me.