Trojan/Virus Processes?
Posted: Fri Jul 16, 2010 11:07 pm
I noticed 3 different processes running on my task manager.
csrss.exe
lsass.exe
smss.exe
From a search on http://www.processlibrary.com to identify their purpose, there are two different answers.
One answer is from Microsoft Corp indicating these processes are critical for the functionality of the OS (XP PRO SP3).
Other sources (from unknown authors) say these processes are likely Trojans or Viruses. With the purpose of stealing sensitive information, for credit card fraud and identity theft.
Microsoft says their normal location is in C/WINDOWS/SYSTEM32. I did a search on all 3 files. And found 2 locations for each. One location is C/WINDOWS/SYSTEM32, and the other location is C/WINDOWS/SERVICEPACKFILES/i386.
Scanned both locations of each type with Microsoft Security Essentials and Malwarebytes. None of the files came up as malicious or infected.
Do I have anything to worry about? I find it kind of strange that there is two locations for each file. However, it seems the 2nd location may have been created during the SP3 update.
What say you?
csrss.exe
lsass.exe
smss.exe
From a search on http://www.processlibrary.com to identify their purpose, there are two different answers.
One answer is from Microsoft Corp indicating these processes are critical for the functionality of the OS (XP PRO SP3).
Other sources (from unknown authors) say these processes are likely Trojans or Viruses. With the purpose of stealing sensitive information, for credit card fraud and identity theft.
Microsoft says their normal location is in C/WINDOWS/SYSTEM32. I did a search on all 3 files. And found 2 locations for each. One location is C/WINDOWS/SYSTEM32, and the other location is C/WINDOWS/SERVICEPACKFILES/i386.
Scanned both locations of each type with Microsoft Security Essentials and Malwarebytes. None of the files came up as malicious or infected.
Do I have anything to worry about? I find it kind of strange that there is two locations for each file. However, it seems the 2nd location may have been created during the SP3 update.
What say you?