Seen the warning about infected sites. It said if there is a possible infected website to post a messgae here about it.
This website gave me a alert for a virus and said to abort the connection.
I did
Here is the website
Welcome to the forums, fireblazin. 
I just visited the site and got no alarms from avast. Do you remember the name of the virus?
Mi è venuto fuori l’avviso di avast per i siti infettati.
I siti potrebbero essere www.facebook.com
oppure www.msn.it
Non riesco a risolvere il problema!
Thanks
It didnt give me a virus name. It just did the alarm sound and said that a virus was dedected and I should abort the conection which I did.
It should have done - Check the avast! Log Viewer (right click the avast ‘a’ icon), Warning section, this contains information on all avast detections. C:\Program Files\Alwil Software\Avast4\ashLogV.exe - Or check the source file using notepad C:\Program Files\Alwil Software\Avast4\DATA\log\Warning.log
When posting URLs to suspect sites, change the http to hXXp so the link isn’t active (clickable) avoiding accidental exposure.
I did not get a warning, but I read about the iframes, and then I tried to go to www.facebook.com today. The blue bar at the top of the window had a bunch of question marks, then the word Facebook, and the screen looked just like the Facebook sign-in, except that everything but the word “Facebook” was in Russian. It’s kind of flipping me out, since I’m running malware detection and updating everything in sight and running Avast and nothing is warning me about bad stuff on my computer. But I don’t usually have websites coming up in Russian. Is this a perfect time to panic, as Woody would say in “Toy Story”?
Hi CreveCoeur,
The reasons for these things happening to sites:
common causes seem to be as follows:
* The website is hosted on a cheap web hosting service
* The website is using an old version of an open source application (eg: WordPress 1.0) which has known security issues
* File permissions on the server are not set accordingly (eg: every file and folder on the server is set to 777 - read-write-execute)
* Weakness in an application code. For example, there is not sufficient input validation.
* FTP rather than SFTP is used
* There is no IP restriction for SSH and FTP accounts
Things webmasters can do:
There are a few simple things that can be done to reduce the risk of your website being attacked.
* Change your passwords periodically (say, at least once a month)
* Keep your applications up-to-date. Always upgrade immediately when a new version is available.
* Clean up files and directories on the web server. Make sure there is no old file with .bak or .txt extensions lying around
* Ensure that appropriate file permissions are used for every file and directory on the web server
* Consult with a security expert to obtain the best advice
And the user: use a browser with proper in-browser protection: Fx with NoScript and RequestPolicy extensions installed and enabled, use avast fully updated and with the shields activated. In case of anything fishy or uncommon come here and report,
polonus (malware fighter)