Timeline for What should you do if you catch encryption ransomware mid-operation?
Current License: CC BY-SA 3.0
21 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Sep 12, 2021 at 23:34 | review | Suggested edits | |||
Sep 13, 2021 at 7:11 | |||||
Apr 5, 2018 at 2:54 | comment | added | forest | @StephenKing An expert holds more authority than a professional. If ransomware is this person's profession, then he is a professional. A professional burglar is still a professional, but they may or may not be an expert burglar. | |
Apr 3, 2018 at 16:00 | review | Suggested edits | |||
Apr 3, 2018 at 16:13 | |||||
Apr 3, 2018 at 15:25 | comment | added | Stephen King | Nearly choked when I read "We are professionals". You're an expert at best, never a professional. | |
May 19, 2017 at 0:59 | comment | added | Nat | -1 for "We are professionals" and "good to go" as these phrases fail to objectively describe the situation. Additionally, this answer fails to address the case in which a victim doesn't want to pay the ransom, in which case stopping the malware as quickly as possible minimizes the portion of their data that's lost. | |
Mar 15, 2017 at 15:28 | history | edited | CommunityBot |
replaced http://meta.security.stackexchange.com/ with https://security.meta.stackexchange.com/
|
|
Apr 29, 2016 at 21:10 | comment | added | Stone True | This presumes you are dealing with competent ransomware authors. How can you tell professionally developed ransomware from some copy cat who cannot even keep the key secret (computerworld.com/article/2489311/encryption/…)? Maybe the ransomware industry needs to have some sort of certification system... ;) | |
Apr 23, 2016 at 2:52 | review | Low quality posts | |||
Apr 23, 2016 at 3:54 | |||||
Apr 19, 2016 at 20:15 | review | Suggested edits | |||
Apr 19, 2016 at 21:33 | |||||
Apr 19, 2016 at 19:18 | history | edited | schroeder♦ | CC BY-SA 3.0 |
deleted 2 characters in body
|
Apr 19, 2016 at 18:43 | history | edited | schroeder♦ | CC BY-SA 3.0 |
link
|
Apr 19, 2016 at 18:34 | history | edited | schroeder♦ | CC BY-SA 3.0 |
added 338 characters in body
|
Apr 18, 2016 at 18:17 | review | Suggested edits | |||
Apr 18, 2016 at 19:12 | |||||
Apr 18, 2016 at 6:26 | comment | added | Fiksdal | @Ángel This is very important. Some ransomwares are so badly written that they fail to actually restore your data, even if you pay. | |
Apr 17, 2016 at 23:18 | comment | added | Ángel | This is certainly the best solution for the ransomware author, any other solution would go against your interests. However, there are many badly-coded ransomwares (and their recovery-tools) that eg. make things worse by encrypting files twice or even make the files irrecoverable. | |
Apr 17, 2016 at 20:49 | comment | added | schroeder♦ | To those who do not think this is an answer, consider this: doing nothing might be the best way to go to ensure that data doesn't get corrupted (depending on how the malware was written). This seems like a perfectly valid suggestion. | |
Apr 17, 2016 at 20:39 | comment | added | schroeder♦ | Oh, and welcome! We have tons of ransomware questions here (as you can imagine) - we'd love to get your feedback and perspective. | |
Apr 17, 2016 at 20:38 | comment | added | schroeder♦ | You can't seriously be suggesting "trust us" as a risk mitigation process ... | |
Apr 17, 2016 at 20:28 | review | Low quality posts | |||
Apr 17, 2016 at 20:52 | |||||
Apr 17, 2016 at 20:03 | review | First posts | |||
Apr 17, 2016 at 20:09 | |||||
Apr 17, 2016 at 20:03 | history | answered | Dasya | CC BY-SA 3.0 |