- Apr 13, 2013
- 3,224
Almost forgot to publish this before I left:
Usually when a malware is blocked it also gets killed. As you see from the video the rest of the malware that was run are not in memory(you see what is running from process explorer window) .impressive.
what does it mean that the last one "remained in memory"? I didn't understand that part.
thanks.Usually when a malware is blocked it also gets killed. As you see from the video the rest of the malware that was run are not in memory(you see what is running from process explorer window) .
Probably the malware is suspended. I am not an expert to tell you how a malware can get out of that state and run. Maybe someone can help with that. In my understanding it can't do anything and will go away on restart but VS should have killed it.thanks.
and what are the practical consequences of it remaining in memory?
So if Voodoo blocks a nasty, it would be a good idea to reboot, just in case.Probably the malware is suspended. I am not an expert to tell you how a malware can get out of that state and run. Maybe someone can help with that. In my understanding it can't do anything and will go away on restart but VS should have killed it.
Not really. If you see one running in memory then maybe restart. Assuming the dev finds the sample he will see why it was not killed and will fix it. Nothing to really worry about. Relax for now.So if Voodoo blocks a nasty, it would be a good idea to reboot, just in case.
Is there a VoodooShield Product thread here, I couldn't find it through search?
I know that And I am active there too with this same dashing usernameI do not know about a thead here on MT , but on wilders there is dan the develloper is also very active in this thread
VoodooShield ?
I know that And I am active there too with this same dashing username
I think will start a VS thread here too