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

Mopping up after ransomware and advice on .micro files


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

#1 Moggyman

Moggyman

  • Members
  • 2 posts
  • OFFLINE
  •  
  • Local time:03:25 AM

Posted 02 February 2016 - 06:58 AM

Hi

 

A newbie here so apologies if this is the wrong place or if my questions are answered elsewhere - I couldn't find much info.

 

I've been given a laptop to 'fix'. I found it was infected with ransomware which had encrypted all the data files and added a .micro extension to them. I work in IT but don't dabble with much security stuff to be honest - certainly not something as nasty and cruel as this. The laptop belongs to an elderly soul who never knew to take backups so all her precious photos etc are garbaged. If I could get my hands on the people who made this, grrrrrrr.............

 

Anyway, I think I've cleared the malware out - scans from various products all report it as clean - which leaves me with the problem of what to do next. I'm currently trying a few file recovery programs to see if Windows 10 has some older hidden file versions tucked away somewhere but I'm not hopeful. I did get a load of stuff back from a utility called Shadow Explorer which looked promising. I restored all the files to a different folder but despite looking OK (in that they had correct sizes, extensions and icons), nothing would open. Each parent app like Paint/Word etc claimed the files to be corrupted. Whether they can be fixed or not I do not know. Any expert advice on that would be much appreciated.

 

I'm now scanning with EaseUS Recovery as I've used that on my own PC with great success and if that doesn't give me anything I'll try Recuva next, which was mentioned in a post I read.

 

Beyond that, am I looking at blatting the whole thing and re-installing Windows 10? I did spot a utility aimed at decrypting files left by this particular malware but as I understand it, at the time of writing you are screwed if you have .micro files. If I do have to vape the laptop maybe I should hive all the .micro files off to storage in case that utility is updated to handle them at some point?

 

Any advice would be welcomed.

 

Cheers 


Edited by hamluis, 02 February 2016 - 02:54 PM.
Moved from AII to Gen Security - Hamluis.


BC AdBot (Login to Remove)

 


#2 quietman7

quietman7

    Bleepin' Janitor


  • Global Moderator
  • 51,288 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Virginia, USA
  • Local time:10:25 PM

Posted 02 February 2016 - 05:45 PM

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. TeslaCrypt 3.0 will leave .html, .txt files (ransom notes) with names like recovery_file_[random].txt, recover_file_[random].txt, Howto_Restore_FILES.TXT and help_recover_instructions+[random].txt.

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.

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.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