Site not flagged by avast shields, flagged by Bitdefender’s TrafficLight…
ASN report scan: http://urlquery.net/report.php?id=1693278 with Detected suspicious URL pattern for that IP…
Yandex periodically checks websites for viruses. The last check (less than three days ago) detected malware on this website. The owner of the site may be completely unaware of any malicious code installed on the site by hackers. If the code is not found the next time the website is checked the tag will be removed.
So the last detection was less than three days ago and avast is a live scan.
WOT is reputation based and I wouldn’t take that at face value either, guidance only.
Well it still is been given as sending live malware (unknown html malware) at clean mx Up(nil): unknown_html RIPE RU abuse at avguro dot com 81.177.139.151 to 81.177.139.151 teatr-sovremennik dot ru htxp://teatr-sovremennik dot ru/ this was at 2013-03-30 01:37:14 CET
The only thing I could do is report to virus AT avast dot com and I just did. Seems the most sensible thing to do and virus analysts there have the last word.
You are right where urlquery dot net does not give any IDS alerts now. There certainly are some baddies on that same IP (with exploit kit launching and exploit kit landing page - Blackhole 2) What abput this one: http://urlquery.net/report.php?id=343594 which also recently has been taken down - I get a 403 error…
403
Ошибка 403. Доступ запрещен
Доступ в эту папку запрещен администратором сайта или в папке нет индексного файла.
Вы можете попробовать вернуться назад или перейти на главную страницу сайта.
Если вы владелец этого сайта, ознакомьтесь с возможными причинами возникновения этой ошибки.
Since avast doesn’t specifically have phishing sites on the VPS only malicious/infected sites, there isn’t a specific way to report them for inclusion in the VPS for Network Shield.
Also see http://forum.avast.com/index.php?topic=82635.0, extract below. Reporting a phishing/malicious/hacked site not detected by the Network/Web Shield/s:
Essentially it is sending an email to virus (at) avast (dot) com (no attachment as there is no physical file) outlining the issue and giving the URL in the body of the email.
The email Subject is probably more crucial as I would say it still has to be called ‘Undetected Malware’ for it to be filtered within the receipt system for action. I would go further and include ‘Network Shield’ in the subject to further define the problem and possibly attract attention. So the subject would be something like “Undetected Malware - Network Shield - Phishing/Malicious site” (whichever is applicable), without the Quotes.
Hope that comes in soon. We will put it on our “wish-list” then.
The more users report, the better and fine-tuned avast! detection will get.
I know that is a thing we both are after…