Other replies have indicated, surely incontrovertibly, that this is some sort of automated framework gone wrong (or wrong-er); but, in that case, I think a question is: what's changed so that that automated framework has discovered 127.0.0.1 now, and not before?