Any files that are encrypted with CryptXXX Ransomware
will have the .crypt
extension appended to the end of the affected filename and leave files (ransom notes) named de_crypt_readme.txt, de_crypt_readme.html, de_crypt_readme.bmp, de_crypt_readme.png. CryptXXX 2.x/3.x variants will leave unique Personal ID files using random 12 hexadecimal characters with names like <id-number>.html, <id-number>.txt, <id-number>.bmp (i.e. S45CC72F3463.txt, !4AD604B8AE89.txt), !Recovery_<id-number>.html, !Recovery_<id-number>.txt, !Recovery_<id-number>.bmp (i.e. !Recovery_4582C8FAEB15.txt).
Any files that are encrypted with CryptXXX 3.x / UltraDeCrypter
will have the .cryp1
extension appended to the end of the affected filename. More information about CryptXXX Version 3.100 is provided in this article
A repository of all current knowledge regarding CryptXXX / UltraDeCrypter
is provided by Grinler
(aka Lawrence Abrams), in this topic: CryptXXX Ransomware Help, Information Guide and FAQ
Several victims of CryptXXX reported they paid the ransom but the cyber criminals did not provide a key to decrypt the files. Victims of CryptXXX 2.x variants have reported that the key and decryption software provided by the cyber criminals did not work or resulted in errors. Victims of CryptXXX 3.x / UltraDeCrypter initially reported the decryption tool did not work but a new decryptor release has been reported to work sometimes.
announced its RannohDecryptor tool
will work for those infected with CryptXXX.
Trend Micro also released a Ransomware File Decryptor
for victims of CryptXXX 2.0 and TeslaCrypt versions 1-4. Trend Micro's website warns that it's decrypter may do only a partial decryption on CryptXXX 3.0 encoded files.
However, Kaspersky's tool will not work
on CryptXXX 3.x / UltraDeCrypter since the malware authors have rendered their free decryption tool ineffective.
CryptXXX updated to version 3.0, Decryptors no longer Work
On May 21st, the developers behind the CryptXXX ransomware updated their code to version 3.0 in order to stop Kaspersky's RannohDecryptor from decrypting files for free. Unfortunately, it appears that this update has also had the unintended consequence of breaking the malware developers decryptor...For those who are affected by CryptXXX 3.0, it is advised that you do not pay the ransom as there is a good chance that you will not receive a working decryptor. You should wait instead to see if Kaspersky is able to update their decryption program to bypass CryptXXX's encryption algorithm.
There is an ongoing discussion in this topic where you can ask questions and seek further assistance. Other victims have been directed there to share information, experiences and suggestions.
Rather than have everyone with individual topics, it would be best (and more manageable for staff) if you posted any more questions, comments or requests for assistance in the above support topic discussion...it includes experiences by experts, a variety of IT consultants, end users and company reps who have been affected by ransomware infections. Doing that will also ensure you receive proper assistance from our crypto malware experts since they may not see this thread. To avoid unnecessary confusion, this topic is closed.
The BC Staff