@tliston I think it was a DNS attack-- the real site is undamaged AFAICT. Google just happened to index the site at the wrong moment.