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.

Photo

file encrypted renamed .MICRO unable to decrypt files


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

#1 murthy6332

murthy6332

  • Members
  • 4 posts
  • OFFLINE
  •  

Posted 07 February 2016 - 10:58 AM

Hello sir,
 
I clicked on a file attached on an email (info.js) after saving it on the desktop. All files were renamed with extra extension .micro (e.g: murthy.xls became murthy.xls.micro
Please help.
Thanks in advance

BC AdBot (Login to Remove)

 


#2 quietman7

quietman7

    Bleepin' Janitor


  • Global Moderator
  • 51,288 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia, USA
  • Local time:06:52 AM

Posted 07 February 2016 - 11:58 AM


You are dealing with the newest variant of TeslaCrypt ransomware...TeslaCrypt 3.0 will have the .xxx, .ttt or .micro extension appended to the end of the filename as described in this news article. 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, 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 and wait for solution.

There is an ongoing discussion in this topic where you can ask questions and seek further assistance.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.

Thanks
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