I think it's called extended data query hit. Something like that.

It is documented in the protocol so Xolox should cope with it. I'm guessing they will next time. They don't have to interpret the extra data, they can just ignore it as long as they still parse the messages properly.