The detection seems to have come from our antivirus engine (the name suggests that). So it was probably reported to the AV vendor and got fixed. Sorry for answering this late.