i run Avast as standard virusscanner, but once a while i do a full scann with Avira:free.
avira found a trojan “Gorshok.A” in the file “clnr0.dll” in my Avast folder. Avast doesen’t detect it.
couldn’t find anything about this one either here or google.
anyone can give me any info about this one, if its a legimate threat or a flase positive?
any help is appreciated, and thanks!
greetings
Why do you say it’s a false positive? Just because avast! doesn’t pick up the trojan doesn’t automatically mean there is no trojan.
I have the same problem as cybersurfer. When I run Avast it says the system is clean but I also did an online scan today using Kaspersky’s online scanner and it detected the following:
C:\Program Files\Alwil Software\Avast4\DATA\clnr0.dll Infected: Trojan.Win32.Gorshok.a
We can’t simply assume it’s a false positive just because Avast doesn’t pick it up. It is after all an Avast file that was infected.
I also Googled that trojan but didn’t have any luck getting sufficient info.
How do I remove the Trojan.Win32.Gorshok.a virus?
Where can I get info on this specific Trojan?
(I obviously don’t want to permanently remove the Avast! software from my computer because it is my primary anti-virus software)
Sorry, there’s a misunderstanding here. I’m not saying the clnr0.dll file is a trojan. I know clnr0.dll is an avast file because I read your reply. I’m saying the file appears to be infected by a trojan. Can’t a normal .dll file be infected by a trojan? Or is a trojan always a separate file on its own? (I don’t know how Trojans work, that’s why I ask)
A trojan generally doesn’t infect other files, that is done by a virus, etc. and a trojan file is usually completely malicious, not a legit file with a small piece of code inserted into it.
Thanks for the link David. I uploaded the avast file clnr0.dll to VirusTotal; see results below. As you can see, 3 detections for Trojan.Win32.Gorshok.a
Maybe this is a brand new trojan so the others can’t check for it yet? What do I do?
Can you perhaps upload your own clnr0.dll file to VirusTotal to see if you get the same results? Maybe if you get it too, and you know your system is clean, we can confirm that these are false positives indeed?
File clnr0.dll received on 12.18.2007 15:46:46 (CET)
Current status: Finished
Result: 3/32 (9.38%)
first, thanks for everyone whos helping out, i know everyones busy before xmas
i did an onlinescan on the above mentioned site, heres the results:
since thers only 3 programms finding anything in this file i thought that i would assume its safe for now and just to continue watching it, but as Globetrotter thinks it might be a new troja, i am not so sure anymore…
. if anyone finds anythign else i will be gratefull for any info!
thanxs again, greets cybersurfer
Well if it is any help the file size, MD5 and SHA1 on my file are identical. So I do think it is an FP by the three as I know for a fact mine isn’t infected, as no globe-trotting or visits to suspect sites.
Kaspersky is picking it up on a few of my PC’s aswell but i do think it is a false positive. As a few of my PC’s haven’t been used at all since I last scanned them with kaspersky so there is no way they could have got infected.
If Kaspersky still detects it after a clean install, then it’s clearly a false positive. But if Kaspersky no longer detects it, as you said above, then the infection was simply removed by the clean install? I’m confused.
Yesterday it still detected it on a clean install, today i have scanned both computers and it doesn’t find it on the new install PC or the old install PC.
So it was clearly an FP, and since yesterday kaspersky have updated there definitions to sort the problem out.
Is clnr0.dll supposed to recreate itself after deletion?
Same thing happened to me when using Antivir as a second scanner and I deleted it before realising that it was an Avast file. clnr0.dll reappeared again after I rebooted my laptop.
It has the same MD5 number as the original poster.
avast has an integrity checker so I’m not sure if that particular file is included but it would seem so.
If you are still using antivir as a second scanner, there could be conflict as it too is a resident scanner unless you hack it about so it isn’t resident.