I think the problem is related to malware coded in Nim to evade antivirus. Just do a quick google search to find news about this. Can negative publicity help to increase the popularity of the Nim language?
https://ilankalendarov.github.io/posts/nim-ransomware/ https://www.cybersafe.news/researchers-found-malware-written-in-nim-programming-language/ https://www.bleepingcomputer.com/news/security/trickbots-bazarbackdoor-malware-is-now-coded-in-nim-to-evade-antivirus/
Yes, but as I already said, this should not occur if AV software vendors did correctly their job. They should detect patterns which are specific to malware and not flag as suspicious any software written in Nim, especially Nim tools.
Of course, from their point of view, it is preferable to get false positives on programs written in a little known language rather than not detect malware. As apparently Nim is going to get some popularity as a language to create malware, I’m afraid that if AV software vendors continue this way, using Nim on Windows will become very painful.
Unfortunately, there is not a big company supporting Nim. If this occurred to Go or Rust, I’m pretty sure that the issue would be solved quickly.
Yes, it would solve the issue regarding Nim compiler and tools. But it would not prevent possible false positives with other programs written in Nim. The AV software vendors must refine their criteria regarding what is actually a malware written in Nim.
Should we search what in the binaries has actually triggered the quarantining? I did that once, but it takes time and it is their job to do that.