Any files that are encrypted with BTCWare AES-256
versions will have the [<email>].blocking
or [<email>]-id-[random hexadecimal characters id].wyvern
, [<email>]-id-[random hexadecimal characters id].payday
, [<email>]-id-[random hexadecimal characters id].shadow
, [<email>]-id-[random hexadecimal characters id] with .wallet
extension appended to the end of the encrypted data filename.
BTCWare Ransomware will leave files (ransom notes) named HOW_TO_FIX_!.txt, #_HOW_TO_FIX_!.hta, #_HOW_TO_FIX.inf, !#_DECRYPT_#!.inf, !## DECRYPT FILES ##!.txt, READ ME.txt, !! RETURN FILES !!.txt, !#_RESTORE_FILES_#!.inf, !#_READ_ME_#!.hta, #_README_#.txt, HELP.hta, HELP.txt.
You can submit (upload) samples of encrypted files, ransom notes and any contact email addresses or hyperlinks provided by the cyber-criminals to ID Ransomware
for assistance with identification
Unfortunately, newer variants of BTCWare are AES-256 versions of the malware which uses a different RSA-1024 key and are not decryptable
unless you pay the ransom and get the private AES key from the criminals. There is no way to bruteforce the key for any of these versions. Read Demonslay335
's comments in Post #293
and Post #432
There is an ongoing discussion in this topic where victims can post comments, 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. To avoid unnecessary confusion, this topic is closed.
The BC Staff