Type
File Name
Location
0kilobypt was first discovered in March 2016 in enterprise cloud environments.
Name
0kilobypt
First Seen
March 2016
0kilobypt is known to target specific file types. Below are all known file types that 0kilobypt is known to infect.
In some cases, ransomware will update the modified date, when it encrypts files. 0kilobypt unknown 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 0kilobypt ransomware is known to change.
Suffixes
.CRYPT, .cr, .val, /.w{8}$/, /.w{5}$/
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 0kilobypt.
Type File Name Location file WHERE ARE YOUR FILES READ ME (ГДЕ ТВОИ ФАЙЛЫ, ПРОЧИТАЙ МЕНЯ).txt file !!!ПРОЧИТАТЬ!!!.txt file ВЕРНУТЬ ВАШИ ФАЙЛЫ.txt file RECOVERY.txt file README.txt file RECOVERY.hta
These are the names of the executables that contain the undetonated ransomware payload for 0kilobypt.
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 0kilobypt.
External Pages