That's one of the fake accelerators out in the web.
The description below blows it all, it just re-broadcasts transactions instead of including them to the block that they're mining.
It must have mistook the error in broadcasting the transaction into thinking that it's already confirmed.

That's only possible if the transaction is also included in his own node,
and the child transaction will also be rejected by those who've rejected the parent because the child's input(s) will be missing in that case.