ransomware includes several known versions with various extensions for encrypted files. Any files that are encrypted with TeslaCrypt 3.0
will have the .xxx
extension appended to the end of the filename as described in this news article
and leave .html, .txt files (ransom notes) with names like recovery_file_[random].txt, recover_file_[random].txt, Howto_Restore_FILES.TXT, help_recover_instructions+[random].txt, _H_e_l_p_RECOVER_INSTRUCTIONS+[3-characters].txt and Recovery+[random].txt.
A repository of all current knowledge regarding TeslaCrypt
, Alpha Crypt
and newer variants is provided by Grinler
(aka Lawrence Abrams), in this topic: TeslaCrypt and Alpha Crypt Ransomware Information Guide and FAQ
Currently, there is no way of decrypting
TeslaCrypt 3.0 .xxx, .ttt, .micro
, or .mp3
variants 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. 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.
You can also post comments in the related BC News article:
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