Post by Captain Zedo on Aug 11, 2011 8:51:55 GMT -5
I can't thank you enough for pointing out a legitimate infection in the sites "Maps" folder. All of the HTML files there had a script attached from the 2004 infection. I had replaced the sites main files, but had ignored this subfolder. I haven't updated maps in years.
I have already uploaded clean pages and checked them on the server. I received word from the server this morning that a check done three days ago showed that there was no malicious programming on the server's OS and database areas. Their security has been heavily upgraded in the past two years.
This does not let Google off the hook. Google got both the type of infection and the pages infected wrong and still does. Google is still claiming my main page is infected and it is not. Google also claimed that I was installing a remote pinger, which this infection (a redirect) did *not*. Those charges could have gotten me arrested.
Also note that Google's blocking will not cease now that the site is cleaned. I have never known a site to get around this without A) Paying Google, or B) changing servers and URLs.
A genuine thanks, though, to all of you who found this problem that I had overlooked.
I have already uploaded clean pages and checked them on the server. I received word from the server this morning that a check done three days ago showed that there was no malicious programming on the server's OS and database areas. Their security has been heavily upgraded in the past two years.
This does not let Google off the hook. Google got both the type of infection and the pages infected wrong and still does. Google is still claiming my main page is infected and it is not. Google also claimed that I was installing a remote pinger, which this infection (a redirect) did *not*. Those charges could have gotten me arrested.
Also note that Google's blocking will not cease now that the site is cleaned. I have never known a site to get around this without A) Paying Google, or B) changing servers and URLs.
A genuine thanks, though, to all of you who found this problem that I had overlooked.