No issue here with the latest Windows Defender definitions (1.251.318.0) from earlier today.
Please make sure that your Defender definitions are up-to-date.
Also make sure that your vorpX is updated to the latest version 17.2.3.
If you still see that issue afterwards, you might have catched a virus elsewhere that infects other .exe files on your PC – although that is quite unlikely.
In general: while Windows Defender is not known to cause such problems usually, false positive detections happen from time to time – especially with more aggresive virus scanners – since vorpX “hooks” into other programs. Such things are best reported to the antivirus-vendor in question as a false positive, so they can fix the problem.