includes several known versions with various extensions for encrypted files such as .ecc, .ezz, .exx, .xyz, .zzz, .aaa, .abc, .ccc, .vvv
as described here
. Any files that are encrypted with TeslaCrypt 3.0
will have the .xxx
extension appended to the end of the encrypted data filename as described in this news article
. TeslaCrypt 4.0
no longer uses an obvious extension for encrypted filenames...see this news article
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 Dencrypted: Flaw in TeslaCrypt allows recovery of encrypted files
. Instructions on how to recover the key for decryption are also included in TeslaDecoder.zip
Support for TeslaCrypt 2.0 (and older versions) is provided in this topic where you can ask questions and seek further assistance.Support for decryption requests is provided here
Decryption instructions for all victims of TeslaCrypt 3.0/4.x (.xxx, .ttt, .micro, .mp3) are provided by BloodDolly here
.Kaspersky Lab's RakhniDecryptor tool
will also work for those infected with TeslaCrypt 3.0/4.x.
Support for TeslaCrypt 3.0/4.0 is provided in this topic where you can ask questions and seek further assistance.
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 one of the above support topic discussions, particularly the last if dealing with one of the newer variants...it includes experiences by experts, a variety of IT consultants, end users and company reps who have been affected by ransomware infections. To avoid unnecessary confusion, this topic is closed.
The BC Staff