Comment by gdynamics

It appears as though it was just fixed. I don't think it was really malware, it was probably some technical error on some Chrome team's part.