today, my copy of avast starting pinging repeatedly
aparently it detected a file in my c:\windows\system32\ folder called ssrrqo.dll, as per its normal actions, it immeadiately and automaticly sent it into my virus chest, but then my system, detecting a system file missing, replaced it, only for avast to detect it again immediately and send it to the chest, in an infinite loop
it only stopped once i told avast to disable its scan for a while
now keep in mind, only yesterday did i do a full system scan (and found nothing, completely clean)
now today, this one file is makeing so much excitement
a process scan revealed that its somehow linked to lsass.dll
now being as i dont see that these files are doing anything they shouldnt (other then automaticly replaceing itself in the event of deletion), and my system seems to be running fine, and that i cant really do anything about this file, i was forced to just set my scans to exclude this one instance of this file
so my question is, did anyone else get something like this? what is it? and is there a way to fix it?
A search for the ssrrqo.dll returns only two hits and they are both in this topic, which for a file in the system32 folder is highly suspect, so based on that alone it looks like a good detection.
but then my system, detecting a system file missing, replaced it, only for avast to detect it again immediately and send it to the chest, in an infinite loop
Are you sure this is a system message and when does it occur (strange if it is immediately) ?
Presumably this is for the ssrrqo.dll file ?
a process scan revealed that its somehow linked to lsass.dll
What kind of process scan ?
Given the search hits on that file name any association with this file is likely to be malicious.
"lsass.exe" is the Local Security Authentication Server. It verifies the validity of user logons to your PC or server. Lsass generates the process responsible for authenticating users for the Winlogon service.
So you may have a winlogon entry for ssrrqo.dll that would inderectly be linked to the lsass.exe file.
The hijackthis log should show this association, it would be an 020 entry in the log.