Please read the thread. Milos, Avast! team, said it was a F/P and it was fixed with VPS 130605-1