VoodooShield/Cyberlock

I found out the answer when a google update tried to run

 

Thanks, Dan, for working tirelessly to resolve the freeze issue. You will get there, I have every confidence in you

Testing 338 now...

 

Avast blocks VoodooShield.exe on 3.38, SUD.

/E

 

Interesting, that WAR intercepted the VS installer....I allowed both in response, but the VS icon disappeared.



So, I did a restart of the laptop, and this time no more intervention by WAR...VS 3.38 beta installed. However, this time I exited VS, before I ran the installer.

 

@VoodooShield

Dan, No freezes so far on 338

Only issue is a Google Chrome update alert that keeps popping up every so often but only gives me option to block ??



More details gives this...

 

OMG, that is probably the funniest thing I have read in several years . The thing is… quite literally every single of the 2500+ modifications that I made to VS in the last couple of weeks SHOULD have actually been detected by their Ai as even safer than it was before.

BTW, the VoodooAi result for winantiransom-setup.exe is 0.1950 .

 

I am going to try to catch up on all of the posts I missed in the last few days... I will skip the freeze posts unless there is something specific that I need to reply to.

Also, I have been playing around with something... I wrote some malware and analyzed the file with a lot of different scan engines, just to see what would happen. The first malware that I wrote simply deleted the entire C drive (in theory anyway), but I am going to write some more that does several other things. If you guys have any ideas on what I should include, please let me know!

 

Hmmmm, that is odd that VS was crashing on the install... if you can let me know how to reproduce this error, that would be cool.

Yeah, for now VS is allowed to be killed in the task manager... once the freeze issue is fixed we will change this.

Yeah, VS automatically builds the whitelist with our patented snapshot technology.

Thank you!

 

Very cool... sorry about the confusion .

 

Cool, thank you!

 

Yeah, there were several memory leaks that I was not aware of... they are fixed now, thank you TH!

 

It must be a new version of the software_reporter_tool.exe (with a different hash), but if this continues, please let me know, thank you!

 

Thank you cache, stapp, fax, Chuck57, faircot, hamo, leno and Tarnak!

 

I guess from a certain viewpoint, there is hilarity to be found, but I didn't see any at the time, that I was seeing those popups.

Battle of the AI's? BTW, where is [your] AI in VS...I can't see it, to run.

 

VS 3.35 ? But, I have 3.38. That is not sequential. Or, am I misunderstanding?

 

Thank you Krusty!

 

Thank you, I appreciate that! Maybe next time we will get 4.5 stars .

 

Hehehe, everyone does this, so I am used to it .

The concept of VS is simple... the computer should be absolutely locked when it is at risk. If by chance, there is a squeaky clean new file, then it might be ok to auto allow (depending on what mode VS is in).

Basically, the security industry needs to change from allow by default to deny by default... and until we do, malware will always be an issue. Thank you!

 

Versions 3.36 and 3.37 have been posted here in this forum. 3.38 is the latest at this point in time.

 

Hehehe, but just like lunarlander said, VS is still and anti-executable. Just because I added VoodooAi, that does not mean that it now falls into the traditional anti-virus category . Thank you!

 

Thank you guest and SHvFl!

 

I am aware, but I have just resumed testing the latest betas. I am trying to find out which one I should be running, without the freeze problem, maybe still occurring.

 

Yeah, I think the WSA / VS combo that TH discovered a while back is one of the best combos on the market... which is why I recommend running WSA with VS . Thank you kees!

 

Thank you LW!

 

Hmmm, I am not sure how to change the icon in the task manager... I can look into it though, thank you!