Wait, what? That's contradictory. How could it be signed by your service with an invalid signature? This sounds like a convenient excuse to deflect the blame.
I think it just means that there is a signature, possibly lifted from a real LoG but it's not a valid signature for the fake LoG.