The information will be decrypted if the sufferer captured the key because it was being despatched to the server during encryption. Decryption key might be git from the Tesla request sent to the server. It is possible if the decryption key was zeroed out and partial key present in key.dat. It isn't potential to do that for versions after TeslaCrypt v2.1.0. Just lately, the authors released TeslaCrypt 4.0 sometime in March 2016. A brief evaluation reveals that the new version corrects a bug that beforehand corrupted recordsdata greater than 4GB. It additionally has new ransom notes and doesn't use an extension for encrypted recordsdata. For the model with extension file title .ezz and .exx, the unique decryption key cannot be recovered without the authors' non-public key, if the decryption key was zeroed out. The model with encrypted file extensions .ccc, .abc, .aaa, .zzz and .xyz doesn't use information recordsdata and the decryption key is just not saved on your computer. When it detects a supported information file, it encrypts it and attaches a new extension to the title of the file. With the release of latest variants of TeslaCrypt, this system makes use of totally different file extensions for the encrypted files.