Any files that are encrypted with CryptXXX Ransomware
will have the .crypt
extension appended to the end of the affected filename and leave files (ransom notes) named de_crypt_readme.txt, de_crypt_readme.html, de_crypt_readme.bmp, de_crypt_readme.png. CryptXXX 2.x/3.x variants will leave unique Personal ID files using random 12 hexadecimal characters with names like <id-number>.html, <id-number>.txt, <id-number>.bmp (i.e. S45CC72F3463.txt) or !Recovery_<id-number>.html, !Recovery_<id-number>.txt, !Recovery_<id-number>.bmp (i.e. !Recovery_4582C8FAEB15.txt). A newer CryptXXX 3.x variant (aka UltraDeCrypter) will have the .cryp1
extension appended to the end of the affected filename and leave files (ransom notes) named !(hex-id).html.
A repository of all current knowledge regarding Crypt0L0cker
(TorrentLocker) is provided by Grinler
(aka Lawrence Abrams), in this topic: CryptXXX Ransomware Help, Information Guide and FAQ
There is an ongoing discussion in this topic where you can ask questions and seek further assistance. Other victims have been directed there to share information, experiences and suggestions.
Rather than have everyone with individual topics, it would be best (and more manageable for staff) if you posted any more questions, comments or requests for assistance in the above support topic discussion...it includes experiences by experts, a variety of IT consultants, end users and company reps who have been affected by ransomware infections. 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