nro 0 Report post Posted May 5 Hi, Can someone help me, please and thank you! [!] No keys were found for the following IDs: [*] ID: FehUqywJ9uEWJET103RMXo6QRMDbXoqREe3rLazu (.roldat ) [*] ID: FehUqywJ9uEWJET103RMXo6QRMDbXoqREe3rLazu (.psd ) Please archive these IDs and the following MAC addresses in case of future decryption: [*] MACs: E4:E7:49:42:1A:26, 0E:96:E6:18:39:C7, 0C:96:E6:18:39:C7, 0C:96:E6:18:39:C7, 0C:96:E6:18:39:C8 This info has also been logged to STOPDecrypter-log.txt _readme.txt Quote Share this post Link to post Share on other sites
GT500 564 Report post Posted May 6 The creator of STOPDecrypter has let me know that he already archived your ID and MAC addresses in case he is able to figure out your decryption key at some point in the future. Quote Share this post Link to post Share on other sites
Amigo-A 18 Report post Posted May 7 Today the STOPDecrypter has been updated with the support of the .roldat extensionhttps://download.bleepingcomputer.com/demonslay335/STOPDecrypter.zip Try decrypting some files first by making a copy of them for test. Quote Share this post Link to post Share on other sites
GT500 564 Report post Posted May 7 8 hours ago, Amigo-A said: Today the STOPDecrypter has been updated with the support of the .roldat extensionhttps://download.bleepingcomputer.com/demonslay335/STOPDecrypter.zip This is correct, however keep in mind that it will only decrypt a victim's files if they have an offline ID. For anyone with an ID that was generated while the ransomware was connected to its command and control servers, they will have to wait for an alternate solution. Attempting to decrypt files when the decrypter isn't able to find a key for your ID will result in corrupt files. Quote Share this post Link to post Share on other sites
