The developer is aware of that. I've asked him various time to fix that issue but still is not fixed, because it's a targeted attack and it's not a really relevant issue right now, considering few people know about VS
Good to see I'm not the only one who thinks that VS is hardly known outside these walls. I had a run in with the developer not so long ago, didn't believe that in the real world VS is unheard of to the real average Joe... Must Thinks his company is as large as Symantec lol.
However, Voodooshield is not persistence and easily killed by "taskkill" command inside a macro code
You're right and the developer should make some line of defense because they already have access to kernel-mode since they have an EV digital signature so by not adding enhanced self defence they are sort of not using their resources to the best of their ability I think, but at the same time I think macro's are flawed in itself and it is better to just not use Microsoft Office, or use it with macro's disabled in the first place if you want to be secure.
I doubt you'll find any macro in the wild which targets VS though. The malware authors I doubt have heard of VS
So with this taken into account, the developer probably doesn't care about doing self-defence and probably has more important things to focus on
