First you aren’t actually scanning sites using VT to check a URL all it is doing is checking it against a list of blacklists. You would need to upload the file to have it scanned.
Wait for an Avast Team Member to explain and give a verdict on this detection.
All versions of RegSeeker being flagged of having this malcode.
My hunch is a falsely flagged UPX packed exe detection! But IP had other malware: https://urlquery.net/report/5519bb86-8f3d-44dc-9397-587e997259eb and that might have a reason to take no chances on that packed UPX executable as well or file was not signed proprerly. But still could well be a FP.
Well the UPX packed file controversy (FPs versus genuine detections) has been around ongoing since 2011.
It is not the first time a packed UPX executable was found to be a FP and it certainly will not be the last.
Kaspersky warned av-vendors not to automattically flag all, but to better discriminate between FPs and the real McCoy.
All avast detection with regseeker are for all of 2017. Remember, avast has some reputation here of serving up FP’s.
Wonder what the final verdict will be then?.
Also it should be taken into the bargain that that same IP was abused for serving malcode.
One and one counts up to two in suh a case. Anyway, let us wait and see…
IF there is a file at the URL, VT will download and scan it.
To see the file scan result, click the icon after the hash at > Downloaded file
see attached screenshot below
Be aware that if the file is in a zip, then the hash and additional file info will not be correct, it will be for the zip and not the file inside
In this case it seems the zip containe multiple files.
If you upload the file to metadefender.com it will unpack and list scan result for all files inside the zip. I think the limit is 500 files inside the zip
If it did download the file, then I would have to ask why there was no alert by avast or the other two that detected it ?
Yet my upload to be scanned of the actual RegScanner_4.0.zip did list the detections, yet the SHA256 is the same as in your image, yet it doesn’t appear to have been scanned.
Ah, I had never noticed that tiny icon, much less what it was for
I went into what I thought was the obvious, the Details Tab only to find it wanting. I would have thought that would been the logical location or a link to the file scan.
Thanks for that explanation on the inner workings of VT.
You know Virus Total scan outlay like the inner lining of your pocket. 8)
Good to have you around in such discussions.
@Pondus, DavidR - Many thanks glad to have learnt something new today (w.r.t VT)
At the time of raising this thread also raised it to hoverdesk and received the below
[i]
Hello
Yes it’s a false positive from Avast because RegSeeker executable is compressed with upx.
Next version won’t be no longer compressed though upx has nothing to do with some kind of virus…
Best regards
Thibaud[/i]
So if needed we could defer adding exclusion signatures until next version is released.
You could try that, but personally I would stick with your existing older version of RegSeeker (I’m still using version 2.7 on my XP System) until Avast do remove the detection. Because Avast is alerting on the Zip file when you try to download it, you would have to set a URL exclusion or disable the web shield, neither I feel worthy of what is just another registry cleaner. CCleaner also has a registry cleaner function.
There was also something I read about unwanted add-on also on installation that would make me wait and or ensure you did a custom install and deselect any unwanted extras.
Currently avast is still alerting on it, bu it is still early for a likely FP.
Could not developer signing and authorative certification come to the rescue to discriminate between benign and benevolent UPX packed and malicious and reverse engineered UPX to go under the malware detection radar.
I can understand one often would take ‘the better safe than sorry’ route and question UPX packed code completely…but not like Norton did and remove it without any notice beforehand.
Hello. I just read the post where you said you whitelisted RegSeeker. Did you only whitelist RegSeeker 4.0? I tried to download both 4.0 and 4.5 and my Avast blocked my access to the URL on both versions. Please advise. Thanks.
I’am able to download and install every version of Regseeker without blocking from Avast. Please, can you share the file which is detected + name of the detection?