VoodooShield discussion

Status
Not open for further replies.
Sunshine-boy said:
@danb
Hey,
Dan can vs has some updated cloud an instance of outdated VT database?
Can you pls consider to update the help document file? it's outdated and some settings changed...
Click to expand...
It's in the process of a Version launch, all will be right as rain very soon. ;)
 
  • Like
Reactions: Cats-4_Owners-2, Syafiq, Deletedmessiah and 3 others
TheMalwareMaster said:
@danb
When you have time, after your break, remember to add self-protection. Some users were waiting for it. Thanks in advance
Click to expand...

I don't really think it's needed. If VS can block all real world nasties whiy is it needed? But if you do it, please don't lock up the whole computer and force a reboot. Just have it protect VS itself. The first effort was a deal breaker for me.
 
  • Like
Reactions: Cats-4_Owners-2, Syafiq, _CyberGhosT_ and 4 others
Peter2150 said:
I don't really think it's needed. If VS can block all real world nasties whiy is it needed? But if you do it, please don't lock up the whole computer and force a reboot. Just have it protect VS itself. The first effort was a deal breaker for me.
Click to expand...
By now, there is just this known VS bypass. There may be other ones: this one is made by a killswitch
 
  • Like
Reactions: Cats-4_Owners-2, Syafiq and TairikuOkami
What a strange notification from Voodoo...
 

Attachments

  • Image 1.jpg
    Image 1.jpg
    65.7 KB · Views: 545
  • Like
Reactions: CoherentCrayon
Peter2150 said:
That wasn't a bypass. That was human stupidity. Kinda like shutting down VS and then complaining it didn't work. Security software can't protect against stupidity.
Click to expand...
That is. The macro was able to kill VS process before it was intercepted

boredog said:
TMM
That was an older version of VS you were using. Have you tried your file using the new version? also why would anyone want to enable that in an XL file?
Click to expand...
Dan said it's not fixed yet
 
  • Like
Reactions: madirish and TairikuOkami
TheMalwareMaster said:
That is. The macro was able to kill VS process before it was intercepted
Click to expand...

I tested the macro. To bypass VS or anything you had to be stupid. First when you opened it in Excell you got the warning to turn on macros. That is the first big stupid. Then when I was given the spreadsheet, I was instructed the spreadsheet had to placed in a certain place.

This was an uncleverly designed POC and nothing you would encounter in the wild.
 
  • Like
Reactions: madirish, roger_m, simmerskool and 3 others
Peter2150 said:
I tested the macro. To bypass VS or anything you had to be stupid. First when you opened it in Excell you got the warning to turn on macros. That is the first big stupid. Then when I was given the spreadsheet, I was instructed the spreadsheet had to placed in a certain place.

This was an uncleverly designed POC and nothing you would encounter in the wild.
Click to expand...
Yeah but, in the end, there should be no trouble for us if he adds self-protection. It's just an other security feature
 
  • Like
Reactions: Solarquest, plat1098 and TairikuOkami
Alright Mr. B, lets get this party started ! lol
Seriously though, he has not come up for air for a while, man am I ready for v.4 to release.
I haven't decided yet but I will either run it beside Sophos Home Beta, or EmsiSoft, combined with
GlassWire, and VS v.4 that will be a solid combo.
Take your time Mr. B, but hurry up :P
 
  • Like
Reactions: Solarquest, brambedkar59, aragornnnn and 4 others
Status
Not open for further replies.

You may also like...