Detecting ransomware
There is disclosed in one example a ransomware mitigation engine, including: a processor; a convolutional neural network configured to provide file type identification (FTI) services including: identifying an access operation of a file as a write to the file or newly creating the file; computing a byte correlation factor for the file; classifying the file as belonging to a file type; determining with a screening confidence that the file type is correct for the file; determining that the screening confidence is below a screening confidence threshold; and circuitry and logic to provide heuristic analysis including: receiving notification that the confidence is below the confidence threshold; performing a statistical analysis of the file to determine a difference between an expected value and a computed value; determining from the difference, with a detection confidence, that the file has been compromised; and identifying the file as having been compromised by a ransomware attack.
1. A method, comprising:
if a first determination determines that a first operation is a write to a file or a creation of the file, performing a second determination of a format of the file;
determining a byte distribution within the file, if the second determination determines the format is unknown or encrypted; and
killing a process or terminating the first operation, if the byte distribution indicates the file is encrypted, wherein the process attempted the first operation.
2. The method of claim 1 , further comprising:
backing up the file to produce a backup file, if a third determination determines that a second operation is a deletion.
3. The method of claim 2 , further comprising:
deleting the backup file, if the second determination determines the format is known or unencrypted.
4. The method of claim 1 , further comprising:
hooking a file write, a new file creation, a file delete, or a cleanup operation.
5. The method of claim 1 , further comprising:
locally caching the first operation, in response to the first operation.
6. The method of claim 1 , further comprising:
subscribing to a cleanup event for the file, based at least in part on the first determination; and
determining whether the file has been tampered with, based at least in part on the cleanup.
7. The method of claim 1 , further comprising:
detecting whether the byte distribution is consistent with the format.
8. A computing device, comprising:
a memory including instructions; and
a processing unit configured to execute the instructions to,
if a first determination determines that a first operation is a write to a file or a creation of the file, perform a second determination of a format of the file,
determine a byte distribution within the file, if the second determination determines the format is unknown or encrypted, and
kill a process or terminate the first operation, if the byte distribution indicates the file is encrypted, wherein the process attempted the first operation.
9. The computing device of claim 8 , wherein the processing unit further is configured to execute the instructions to back up the file to produce a backup file, if a third determination determines that a second operation is a deletion.
10. The computing device of claim 9 , wherein the processing unit further is configured to execute the instructions to delete the backup file, if the second determination determines the format is known or unencrypted.
11. The computing device of claim 8 , wherein the processing unit further is configured to execute the instructions to hook a file write, a new file creation, a file delete, or a cleanup operation.
12. The computing device of claim 8 , wherein the processing unit further is configured to execute the instructions to locally cache the first operation, in response to the first operation.
13. The computing device of claim 8 , wherein the processing unit further is configured to execute the instructions to subscribe to a cleanup event for the file, based at least in part on the first determination, and to determine whether the file has been tampered with, based at least in part on the cleanup.
14. The computing device of claim 8 , wherein the processing unit further is configured to execute the instructions to detect whether the byte distribution is consistent with the format.
15. A non-transitory, computer-readable storage medium having stored thereon instructions that, when executed by a computing device, cause the computing device perform a method comprising:
if a first determination determines that a first operation is a write to a file or a creation of the file, performing a second determination of a format of the file;
determining a byte distribution within the file, if the second determination determines the format is unknown or encrypted; and
killing a process or terminating the first operation, if the byte distribution indicates the file is encrypted, wherein the process attempted the first operation.
16. The storage medium of claim 15 , wherein the method further comprises:
backing up the file to produce a backup file, if a third determination determines that a second operation is a deletion.
17. The storage medium of claim 16 , wherein the method further comprises:
deleting the backup file, if the second determination determines the format is known or unencrypted.
18. The storage medium of claim 15 , wherein the method further comprises:
hooking a file write, a new file creation, a file delete, or a cleanup operation.
19. The storage medium of claim 15 , wherein the method further comprises:
locally caching the first operation, in response to the first operation.
20. The storage medium of claim 15 , wherein the method further comprises:
subscribing to a cleanup event for the file, based at least in part on the first determination; and
determining whether the file has been tampered with, based at least in part on the cleanup.