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. Any files that are encrypted with TeslaCrypt 2.0
(AlphaCrypt) will have the .ezz
extension appended to the end of the filename. Any files that are encrypted with the original TeslaCrypt
will have the .ecc
extension appended to the end of the filename.
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
Information for decrypting files with .ecc, .ezz, .exx, .xyz, .zzz, .aaa, .abc, .ccc, or .vvv extensions can be found in this BC News article: TeslaCrypt Decrypted: Flaw in TeslaCrypt allows recovery of encrypted files
. Instructions on how to recover the key for decryption are also included in TeslaDecoder.zip
There currently is no way of decrypting
TeslaCrypt 3.0 .xxx, .ttt
, or .micro
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 and .micro 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, send BloodDolly
a private message with a link to few encrypted files after uploading them to SendSpace (see instructions in Post #1
) and wait for solution.
There is an ongoing discussion in this topic where you can ask questions and seek further assistance.Support for decryption requests can be posted in this topic
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 one of those topic discussions, particularly the last if dealing with one of the newer variants. 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