We have seen this exact issue before, and so far we have never been able to trace it back to our products unfortunately… Here is a recent instance: