Bitdefender antimalware researchers have put together a checklist of things to do to avoid getting infected with Cryptowall.
Cryptowall is a form of ransomware that uses the same encryption and extortion mechanisms as a previous threat, dubbed Cryptolocker. Local files are encrypted using a randomly generated 2048-bit RSA key pair that’s associated with the infected computer.
While the public key is copied on the infected computer, the private key can only be obtained by paying for it within an allocated amount of time. If payment is not delivered, the private key is supposed to be deleted, leaving no possible unencrypting method for recovering the locked files.
One of the most common infection vectors relies on drive-by-attacks through infected ads on legitimate websites, but it has also been known to infect via infected downloaded apps.
Cryptowall infection can be limited and sometimes prevented with:
Best practices
- Use an antivirus solution that’s constantly updated and able to perform active scanning;
- Schedule file backups – either locally on in the cloud – so data can be recovered in case of corruption;
- Follow safe internet practices by not visiting questionable websites, not clicking links or opening attachments in emails from uncertain sources, and not providing personally identifiable information on public chats rooms or forums;
- Implement / enable ad-blocking capacities and anti-spam filters
- Virtualize or completely disable Flash, as it has been repeatedly used as an infection vector
- Train employees in identifying social engineering attempts and spear-phishing emails.
Aside from these general recommendations, you should also:
Enable software restriction policies.
System administrators need to enforce group policy objects into the registry to block execution from specific locations. This can only be achieved if you’re running a Windows Professional or Windows Server edition. The Software Restriction Policies option can be found in the Local Security Policy editor.
After clicking the New Software Restriction Policies button under Additional Rules, the following Path Rules should be used with “Dissallowed” Security Level:
o “%username%\\Appdata\\Roaming\\*.exe”
o “%appdata%\Microsoft\Windows\Start Menu\Programs\Startup\\.*exe”
o C:\\<random>\\<random>*.exe
o “%temp%\\*.exe”
o “%userprofile%\\Start Menu\\Programs\\Startup\\*.exe”
o “%userprofile%\\*.exe”
o “%username%\\Appdata\\*.exe”
o “%username%\\Appdata\\Local\\*.exe”
o “%username%\\Application Data\\*.exe”
o “%username%\\Application Data\\Microsoft\\*.exe”
o “%username%\\Local Settings\\Application Data\\*.exe”
Setting these mechanisms in place could limit or block Cryptowall.
Need the quotes to be included? The GPO editor does not accept them. Further: is %username% correct, shouldn’t that be %userprofile% ?
[…] Do Your Bit to Limit Cryptowall […]
Rule_ C:\\\\*.exe will not apply. It says the path cannot contain the characters. Please clarify.
Regarding my response above, part of the rule was left out in the post. I was referring to the rule with “random” in the path.
You need %USERPROFILE% because it includes the PATH on the hard drive. %username% just has that, the username.
Example:
%userprofile% translates to c:\users\Local User
%username% translates to Local User
Hope this helps
Thank you for taking the time to provide the public with this article.
[…] CryptoWall infections, including keeping a copy of the data on external drives. Read more about it here. To add extra protection, Bitdefender has also developed the CryptoWall Immunizer, a tool that […]
[…] Cryptowall infections, including keeping a copy of the data on external drives. Read more about it here. To add extra protection, Bitdefender has also developed the Cryptowall Immunizer, a tool that […]
[…] offers some additional excellent CryptoLocker/Wall tips here. Their suggestions […]
How do you correctly apply the C:\\\\*.exe rule? Since we cannot guess what the folder name and executable will be when infected? TIA
Sorry, with my response above i meant the “random” file path in c:\ ..