Type
File Name
Location
Crypt0L0cker was first discovered in August 2016 in enterprise cloud environments.
Name
Crypt0L0cker
First Seen
August 2016
Crypt0L0cker is known to target specific file types. Below are all known file types that Crypt0L0cker is known to infect.
In some cases, ransomware will update the modified date, when it encrypts files. Crypt0L0cker updates the last modified date of the file it targets.
Some ransomware will change or append a suffix to the end of the file after they are encrypted, including changing the extension of a file. Here are some of the possible suffixes that Crypt0L0cker ransomware is known to change.
Suffixes
.encrypted, .enc, /.[a-z]{6}$/
Not all ransomware leaves a note. However, some ransomware leaves the infected party instructions on what the user should do to get rid of the ransomware, or satisfy the ransom. This often involves transferring money, often bitcoin or another cryptocurrency to a designated wallet.
Below are the type(s) of notes, content, and typical locations where Elastio has found ransom notes from Crypt0L0cker.
Type File Name Location file COMMENT_RESTAURER_DES_FICHIERS.txt file Wichtige Information zum Wiederherstellen der Daten.htm Desktop file HOW_TO_RESTORE_FILES.txt EveryFolder file DECRYPT_INSTRUCTIONS.TXT file SIFRE_COZME_TALIMATI.txt
These are the names of the executables that contain the undetonated ransomware payload for Crypt0L0cker.
Executables
oqezujlg.exe, Send Bug Report, file.exe, file[1].exe, aa, VigXwo.vsd, encrypt2.exe, myfile.exe
Ransomware often links to external pages such as payment pages, telegram contacts, etc. Below are some of the URLs Elastio has found to be associated with Crypt0L0cker.
External Pages
