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.


virus that changed all file extensions to .lol!

  • This topic is locked This topic is locked
2 replies to this topic

#1 GregCLC


  • Members
  • 13 posts
  • Local time:12:46 PM

Posted 01 February 2016 - 01:15 PM

Our system got hit with a virus that changed all file extensions to .lol! and left a text file named "How to get data" stating it was some form of ransomware.  I'm not sure the virus is actually a crypto virus even though the text file calls itself one. Normally with a ransomware you can check the owner on an encrypted file and see where the infection started from; this isn't the case with this virus for us.  The owner is not changing, the date modified of affected files is not changing.  This seems more like a previous virus I've seen that just changes the file extension, and corrupts the data, rather than actually encrypting. 
Does anyone have any ideas of how to determine which station the infection started on, in a network environment, so that we can make sure we are preventing a re-infection? We will be fine restoring all our data, we have plenty of backups. Unfortunately, this also seems to have hit our View and Security servers, so we can't recompose any of our VMs (another reason I don't think it is ransomware, it didn't hit all our shares, and it hit servers that don't have shares), so we have to find the source and kill it. Any ideas would be greatly appreciated. 

BC AdBot (Login to Remove)



#2 VirusD


  • Members
  • 84 posts
  • Local time:04:46 PM

Posted 05 February 2016 - 10:31 AM

I had this issue before and I was able to deduce what account was responsible by looking at the owner of the ransomnote. I would imagine that if the owner was not changed, then perhaps that IS the account responsible. In my case, it was a temp account that had RDP access to a terminal server. I was sure of this because the temp account was the owner of the ransomnote and on the server I checked, it was that only account on any computer on any account on the network to have the ransomnote ALSO on the local profile directories.


I hope this helps.

#3 quietman7


    Bleepin' Janitor

  • Global Moderator
  • 50,710 posts
  • Gender:Male
  • Location:Virginia, USA
  • Local time:04:46 PM

Posted 05 February 2016 - 02:57 PM

This .LOL! ransomware infection appears to be related to Symantec's description of OMG! Trojan.Ransomcrypt.G which uses the same “how to get data.txt” file with a P.S. Remember, we are not scammers... and string of random characters at the end.

This infection is just another variant of the Gpcode ransomware which has been around for years, uses a secure encryption algorithm and has never been decryptable.There is an ongoing discussion in this topic where you can ask questions and seek further assistance.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.

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