This is a issue with Bitdefender. There is nothing to worry about the same. I had sent a mail about the issue to their technical team. They replied that the issue lies with bitdefender in scanning...