Software Review Comodo FW bypass malware the sandbox (sandbox hips off + on) and voodooshield (autopilot)

Reviews reflect the reviewer's setup and methods. Check the evidence and limitations.
There so many possible instances that Comodo Sandbox may bypass like:
  • Influence of cloud rating
  • Signatures
  • Behavior pattern
But in such concept, any file no matter if file-less or what so over; once run on sandbox then anything will be intact virtualized thus the traces will not cause leakage.

For sure it can be human error or such mistaken to the configuration. unless I'm wrong.
 
No, why do you say that? He just said that the other AI engines also didn't detect the malware.

I don't think so.
I think the dev just meant that it's not only VAi that got the file as "safe" because even those 3 marked the file as safe.
I thought he was talking about Voodoo AI, instead he was meaning those other AI engines. I understood, thank you
 
Maybe as Cruelsister stated you cannot run both together, both are similar in their actions, therefore Voodooshield could be blocking Comodo, but you are unaware of it.

I have seen " comodo virtual service manager" getting turned off at times if you install comodo after installing voodoo. I don't know for sure if this is reproducible or is the cause of misbehavior.
 
I have seen " comodo virtual service manager" getting turned off at times if you install comodo after installing voodoo. I don't know for sure if this is reproducible or is the cause of misbehavior.
I was running a CFW and VS combo at the time that this video was published, and the comodo virtualization worked just fine
 
voodooshield not already bypassed by malware
1) Large detection VT
2) The suspiciously for UI
3) Maybe Even the developer took Precautions against bypass in cloud UI
These are my guesses
4)Maybe even with Comodo voodooshield together produced a mistake.

Testing the free version (lockdown) with modifications + premium (lockdown)+ autopilot everything clean

Try again later samotny Comodo Firewall .-))

thanks for watching

part1)
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.


After rebooting pc

part2)
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Last edited:
comodo has once again shown itself to be buggy and produce unpredictable behavior.
at least voodooshield is trying to learn from mistakes

Valkyrie recognize the file as malware, but it still takes commodes FW file as safe (Installer) file? How is it possible.

Well, I tested AutoSandbox it is useless again be infected because the file is safe by Comodo.A sandboxed not like yesterday.

Advanced File Analysis System | Valkyrie

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
David- at 22 seconds of the video above (and at 22 seconds of the original video) there is a Sandbox setting in the 3rd position. This is a general setting that had to be created as it is not default. At Default Comodo would only have the General settings in positions 4, 5, and 6.

As a comparison look at the 49 second mark of my video (post 29). You can disregard the first 2 (Ignore) as these are specific to SeaMonkey and Java.

So where did this General Rule on your video come from?
 

MalwareTips community

Join the discussion

Create a free account to reply to this thread, ask your own questions and get help from the community.

  • Reply and ask questions
  • Get alerts when someone answers
  • Free malware removal help

Join 75,679 members who help each other for free, since 2010.

Create free account
or continue with

Recently browsing

Members and guests who viewed this thread in the last 5 minutes

Back
Top