Can anyone confirm or deny that NOD is the reason for this problem?

I'ved had this problem recently with a customers pc and had just scanned and cleaned their pc with NOD...


http://www.experts-exchange.com/Security/Win_Security/Q_21344327.html

 

Sign Up to See This Solution ?? huh? Main reason results on this site are the last I ever click on when googling...

 

You don't have to sign up, just scroll down a bit (quite a bit) and then you see the answers anyway.

 

There seems to be no reason to think that NOD is the problem. Reading the accepted answer, it looks like NOD was a solution to the problem. So I don't understand the OP's title for this thread

 

Hi
when it comes to a situation that I think NOD is involved. simply I uninstall NOD and find out. NOD is a very kind program it uninstalls it self quite easily and cleans it self too apart from "ESET folder" which can manualy be deleted after the restart.

 

To me, it sounds like the problem was caused by a couple of trojans that slipped through NOD32's defenses. At least, NOD32's defenses in April. I am not sure if it has been updated to catch these trojans now or not.

To answer the original question, I will deny that NOD32 is the reason for this problem. The problem was caused by the Win32/Exploit.DComRpc.B and Win32/Zapchast trojans.