@nak We believe we found the cause of this issue. The developers have just released a fix:
https://vulndetect.org/topic/472/release-secteer-vulndetect-personal-and-backend-2018-12-28

Please let me know if this fixes it (you only need to wait and see if it runs the inspection at the next "inspectionWindow").