[b]Only three av will detect[/b] (one of which is good old avast!)
well.... only fresh info is correct info ;)
https://www.virustotal.com/nb/file/607255ccc56416deafe9d9029c7a8d0d9ff6b0fc07ba6e7ba2f9a04eec4708d4/analysis/1403126193/
The site offered the Heartbeat TLS extension prior to the Heartbleed disclosure. The extension is now disabled, but the server is still using the same certificate.
LastPass gives it clean, probably based on more recent information:
Site: www.virustotal.com
Server software: Google Frontend
Was vulnerable: Possibly (might use OpenSSL, but we can't tell)
SSL Certificate: The current cert appears to have been reissued recently, likely now safe (2 weeks ago)
Assessment: Certificate now looks safe, go ahead and change your password
Another example where avast! Web Shield correctly detects and blocks JS:Agent-BDA[Trj] in the browser executable, threat comes from here: Object: htxp://www.buah-ara.blogspot.com/
SHA1: 50b1069472df5906b9e160b072c7bcb67011c6ac
Name: TrojWare.JS.Agent.JM
iFrame malware here: htxp://coherence090611.cocolog-nifty.com/JSTAG_3[d46][108] infected with JS.IFrame.312
avast! Web Shield blocks and detects as JS:Iframe-EO[Trj]
we are being protected,
Due to interference of direct avast! Web Shield blocking of code detected, Dr Web’s url checker scan and several others cannot connect and won’t give scan results.
Well, there’s a workaround for that. Set up more than one system running other major a/v’s that don’t block or detect what avast! does, and you can see what scan results you’re not seeing. Think that’s a good way to do it. Of course, you might have to reload your os more often…