@ Tech
First you have to be reasonably confident that if there is something malicious on that page you are able to deal with it or limit the potential for damage. Plus avast standard shield and SAS as resident AS and as a last resort you need a system recovery plan, back-up disk images. Better still would be a virtual environment that can be killed if needs be.
I had to pause the web shield to be able to display the page, in firefox (with noscript, plus running under DMR) there is a simple right click option in firefox to view page source this is also in IE but there is no way I would use IE for this sort of thing. Then check the page source for <script> tags and or <iframe> tags, now you are looking for them to be in strand locations before the start of the page code <html> tag or after the end </html> tag, e.g. not following html standards, etc.
You are also looking for suspect code, such as that I posted before. It isn't difficult, you have to be very careful and need a little experience of html. Or as I say a little knowledge is dangerous
you could get in trouble trying to find any suspect code so the precautions should take priority.
@ polonus
I'm not trying to frighten anyone (bit strange coming from polonus
), merely trying to point out what avast may be alerting on, nothing more, nothing less.
Yes it is doing a document write but that could well be a url to be used, but why obfuscate the code, you have to ask why and what they are trying to hide