Browser Hijacker Deskbar

Tews said:

Dont ya just love image backups??

Absolutely, imaging is the only way to go. And do it frequently.

PS: Of course I upated the Malwarebytes definitions. I always do with all scanners.

Product FRED said:

Yeah, I was gonna ask the same. Did you update your definitions? Also, delete any backups more recent than the one you used since the virus could have been backed up in them (system restore points).

Fred, I don't use restore points (shadows) - only images. I am on a SSD and space is scarce.

tw33k said:

I'm not surprised MSE failed but MalwareBytes? Hate to ask but you did update the definitions before scanning right?

Is there any particular reason why Malwarebytes should have caught it? It may be very good but it is no god.

Malware Research Group

malexous said:

tw33k said:

I'm not surprised MSE failed but MalwareBytes? Hate to ask but you did update the definitions before scanning right?

Is there any particular reason why Malwarebytes should have caught it? It may be very good but it is no god.

If it hasn't been seen by or uploaded to any AV/AM vendors then it won't be in their database to detect/remove.

You could try Combofix to get this one sorted but it is an awfully powerful removal tool and one that I usually use as a last resort.

Jaxryley said:

malexous said:

tw33k said:

I'm not surprised MSE failed but MalwareBytes? Hate to ask but you did update the definitions before scanning right?

Is there any particular reason why Malwarebytes should have caught it? It may be very good but it is no god.

If it hasn't been seen by or uploaded to any AV/AM vendors then it won't be in their database to detect/remove.

You could try Combofix to get this one sorted but it is an awfully powerful removal tool and one that I usually use as a last resort.

Thanks for the tip, but I solved it by restoring an earlier image.

whs said:

Jaxryley said:

malexous said:

Is there any particular reason why Malwarebytes should have caught it? It may be very good but it is no god.

If it hasn't been seen by or uploaded to any AV/AM vendors then it won't be in their database to detect/remove.

You could try Combofix to get this one sorted but it is an awfully powerful removal tool and one that I usually use as a last resort.

Thanks for the tip, but I solved it by restoring an earlier image.

I would do the same as whs - try to deal with the malware to see what works/what doesn't and then restore an image whether I thought that it was successfully dealt with or not.

Jaxryley said:

malexous said:

tw33k said:

I'm not surprised MSE failed but MalwareBytes? Hate to ask but you did update the definitions before scanning right?

Is there any particular reason why Malwarebytes should have caught it? It may be very good but it is no god.

If it hasn't been seen by or uploaded to any AV/AM vendors then it won't be in their database to detect/remove.

Malwarebytes, according to whs, did not find it. Surely there are lots of malware out there that Malwarebytes won't detect, therefore, I don't see why tw33k is surprised.

After running for about 10 hours with the restored system I ran SAS again and am pleased with the result.