ransomware will leave .html, .txt files (ransom notes) with names like recovery_file_[random].txt, recover_file_[random].txt, Howto_Restore_FILES.TXT, help_recover_instructions+[3-random].txt
, Recovery+[5-random].txt, _ReCoVeRy_+[5_random].txt, Recovery_[5_random].txt, _H_e_l_p_RECOVER_INSTRUCTIONS+[3-random].txt, and RECOVERY.TXT.
Files encrypted with TeslaCrypt 3.0 will have the .xxx
extension appended to the end of the filename as described in this news article
. More information about the .mp3
variant is described here
Currently, there is no way of decrypting
TeslaCrypt 3.0 .xxx, .ttt, .micro
, or .mp3
variants unless you pay the ransom since they use a different protection/key exchange algorithm, a different method of key storage and the key for them cannot be recovered. The .xxx, .ttt, micro and .mp3 variants do not have a SharedSecret*PrivateKey so they are not supported by the current version of TeslaViewer. The tool can decrypt TeslaCrypt 3.0 files only if you have the private key
acquired from the malware developer after paying the ransom. If infected with any of these extensions, backup all your encrypted files and wait for a possible solution
There is an ongoing discussion in this topic where you can ask questions and seek further assistance but as noted above there is no solution to fix your encrypted files yet.
Rather than have everyone start individual topics, it would be best (and more manageable for staff) if you posted any questions, comments or requests for assistance in that topic discussion. 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