Jump to content


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.

Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.


Victim of Tesla Crypt

  • This topic is locked This topic is locked
1 reply to this topic

#1 SharonY


  • Members
  • 1 posts
  • Local time:08:53 AM

Posted 11 April 2016 - 02:46 AM

My company's data server got hit last Friday.

We are a small company from Taiwan and are desperate to decode our files to return to our normal routines.

I found this forum very helpful so I joined and hope to find a solution to get things back on track soon.

It's a fairly large and old database so the road to recovery is steep and tough.

BC AdBot (Login to Remove)


#2 quietman7


    Bleepin' Janitor

  • Global Moderator
  • 51,889 posts
  • Gender:Male
  • Location:Virginia, USA
  • Local time:07:53 PM

Posted 11 April 2016 - 04:51 PM

TeslaCrypt 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, .ttt, .micro or .mp3 extension appended to the end of the affected filename as described in this news article. More information about .mp3 variant is described here. TeslaCrypt 4.0 no longer uses an obvious extension for encrypted filenames...see this news article.

- TeslaCrypt 4.0 will leave files (ransom notes) with names like RECOVER+[random].TXT, RECOVER[5-random].TXT, recover_file.txt, _rEcOvEr_[5-random].txt, +-HELP-RECOVER-+[5-random]-+.txt, +REcovER+[5-random].txt and {RecOveR}-[5-random]__.txt.

- TeslaCrypt 3.0 will leave 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, _recovery_+cryptolocker.txt, RECOVERY.TXT.

- TeslaCrypt 2.0 will have the .ezz/.exx extension appended to the end of the affected filename and will leave files (ransom notes) with names like HELP_TO_SAVE_FILES.txt and RECOVERY_FILES.TXT.

- The original TeslaCrypt will have the .ecc extension appended to the end of the affected filename and leave ransom notes with names like RECOVERY_KEY.TXT, HELP_RESTORE_FILES.txt and HELP_RECOVER_FILES.txt. At least one version is disguised as CryptoWall.

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.

Currently, there is no way of decrypting TeslaCrypt 3.0 .xxx, .ttt, .micro, .mp3 variants or TeslaCrypt 4.0 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/4.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.

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 ia provided here:Support for TeslaCrypt 3.0/4.0 is provided 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 one of those support 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
Windows Insider MVP 2017-2018
Microsoft MVP Reconnect 2016
Microsoft MVP Consumer Security 2007-2015 kO7xOZh.gif
Member of UNITE, Unified Network of Instructors and Trusted Eliminators

If I have been helpful & you'd like to consider a donation, click 38WxTfO.gif

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users