Translate

Wednesday, November 6, 2013

The latest and greatest ways to block CryptoLocker.

I've written quite a few blog posts about this ransomware. So by now I am just going to assume that everyone has read it. And odds are, if you are reading, you know what it is anyway.

There are now two ways that can be used to block CryptoLocker from encrypting your files. One of which I have already talked about, but for the sake of convenience, I will talk about it here as well.

The first way is a tool that blocks the execution of the ransomware. Because the ransomware executes from appdata, which is not a place where many applications execute from, this can be used against the ransomware by blocking anything from running from appdata.

This tool was made by FoolishIT and can be downloaded here: www.foolishit.com/download/cryptoprevent/

For more info on this tool, go here: http://www.foolishit.com/vb6-projects/cryptoprevent/


The second way is a way to block the ransomware from encrypting your files.

This way is part of the public beta of HitmanPro.Alert and can be used along with the first method of blocking CryptoLocker.

HitmanPro.Alert was made by SurfRight, and you can find more info and download the beta here: http://www.surfright.nl/en/cryptoguard

Please note that these tools can be used together without any conflicts arising. It is also important to note that these tools can only help you if you are not infected with CryptoLocker. They will not help you if you are already infected.

With both the anti-malware community and the mainstream media being on high alert from this ransomware, I can see a turn in the tide happening soon against this ransomware. Although I cannot forecast in what way it will take form, I know that it will happen.

Whoever made this ransomware has angered too many to continue infecting people. Sooner or later, the good guys win. This is how it has always been, and this is how it will continue.

Thank you for reading, I invite readers to comment if you have any questions or comments.

No comments:

Post a Comment