- Nov 19, 2014
- 2,350
On a more serious note thanks for the Sandboxie ELI5 explanation. I must admit it's not exactly how i understood it worked.
Yes, I'd be interested in this too. Back on topic though, It's completely unrealistic to think that any security can't be bypassed. If someone has the knowledge and experience they'll bypass anything. As Wave stated, Comodo Sandbox is sophisticated, so, someone with the ability to bypass it may very well have the experience to bypass whatever they choose. Thinking ANY security software cannot be bypassed is just naive, just because something hasn't been bypassed at all, or it's been bypassed once a long time ago doesn't mean it can't happen. And no matter what your security config, someone with both the knowledge and experience will bypass everything you've got, And some of those people do it just for fun.I would like to know how Kaspersky TAM reacts to this little monster
It didn't have a sig. It was just added in trusted files by mistake.I am still not clear on the facts of the case.
As far as I understand, at the time of the test it was completely undetected on VT.
And it was (mistakenly) on COMODO trusted list, although this was corrected shortly afterward.
But did it have a digital sig, and if so, was it a valid one?
Nice debate.
By the way, according to your desktop picture on your first post i'm just curious. Did you test the malware on your regular system?
so if it had no sig, let's ask about voodoo autopilot. Is that expected behavior, to allow an unsigned file that is clean on VT? I am assuming that voodoo Ai failed in this case.It didn't have a sig. It was just added in trusted files by mistake.
what layer of CIS would have blocked it, if it had trusted status?
could you elaborate on the config issue?For any that are interested-
1 As I intimated in my video I believe that there was a Configuration issue in the original video post.
For any that are interested-
1). This file was NEVER EVER trusted by Comodo, especially as it was new and unsigned. As I intimated in my video I believe that there was a Configuration issue in the original video post.
2). Sandboxie, although allowing the Textbox popup, will prevent schtasks.exe from running thus (like Comodo) stopping the process cascade.
3). Qihoo will also detect and stop the schtasks mechanism resulting in no system changes.
The moral of the story is to maintain a healthy suspicion of the unknown, and not rely on the gods or technological wonders to protect you.
FYI verdict changed to malware.
http://i.imgur.com/HK7aHB5.png
Disable the scan checkbox in VS settings , you should have a prompt.
He's using Proactive config isn't he? If so that box will already be tickedInteresting !!
Try this option then test file again