# US 2026/0099600 A1 · Ransomware attack onset detection

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0099600 A1
- Document ID: US20260099600A1
- Status: Published application
- Kind: A1
- Application number: 19/406,002
- Filed: 2025-12-02
- Published: 2026-04-09
- Earliest claimed: 2017-08-02
- Assignees: CrashPlan Group LLC
- Applicants: CrashPlan Group LLC
- Inventors: Ajaykumar Rajasekharan; Matthew Mills Parker; Daniel L. Sullivan
- Web page: https://patentgrep.com/patent/US20260099600A1

## CPC

- G06F 21/565: {by checking file integrity}
- G06F 21/554: {involving event detection and direct action}
- G06F 2221/034: Test or assess a computer or a system
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method of detecting the onset of a ransomware attack is presented. In an example embodiment, file backup metadata for each of a plurality of computing devices is accessed and analyzed to detect anomalous file backup activity of individual ones of the computing devices. A determination is made as to whether the detected anomalous file backup activity of at least some of the computing devices is correlated in time. File description metadata for each of the computing devices is also accessed and analyzed to identify files in the computing devices that are anomalous to other files in the computing devices. A determination whether a ransomware attack has begun is based on a determination that the detected anomalous file backup activity of at least some of the computing devices is correlated in time, as well as on the identified anomalous files.

## Claims

### Claim 1

A method for detecting a ransomware attack or unauthorized encrypting of files, the method comprising:
analyzing, using at least one hardware processor of a machine, file backup metadata of a plurality of computing devices to detect a first anomalous file backup activity event and a second anomalous file backup activity event on at least one computing device of the plurality of computing devices, wherein each of the first and second anomalous file backup activity events are detected based on identifying a sudden change in addition of files and a sudden change in deletion of files since a most recent backup operation, and wherein the first and second anomalous file backup activity events include an associated detected time;
determining that the first anomalous file backup activity event and the second anomalous file backup activity event are correlated based on determining the associated detected time of the first anomalous file backup activity event and the associated detected time of the second anomalous file backup activity event are within a predetermined time period of each other;
accessing file description metadata for the at least one computing device of the plurality of computing devices;
analyzing the accessed file description metadata to identify anomalous files; and
determining that a ransomware attack or unauthorized encrypting of files has begun based on the determination that the first anomalous file backup activity event and the second anomalous file backup activity event are correlated and based on the identified anomalous files.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
analyzing the file backup metadata to detect a third anomalous file backup activity event at another computing device of the plurality of computing devices;
determining that the third anomalous file backup activity event is correlated with the first anomalous file backup activity event and the second anomalous file backup activity event;
accessing file description metadata for the another computing device;
analyzing the file description metadata for the another computing device to identify anomalous files at the another computing device; and
wherein the determination that a ransomware attack or unauthorized encrypting of files has begun is further based on the determination that the third anomalous file backup activity event is correlated with the first anomalous file backup activity event and the second anomalous file backup activity event and further based on the identified anomalous files at the another computing device.

### Claim 3 (depends on 1)

The method of claim 1, wherein the file description metadata comprises file extensions, wherein analyzing the file description metadata to identify anomalous files at the at least one computing device of the plurality of computing devices comprises determining file extensions of the anomalous files at the at least one computing device are different than file extensions of other files at the at least one computing device.

### Claim 4 (depends on 1)

The method of claim 1, wherein the file description metadata comprises at least one of a filename, a file MIME type, a file size, a file hash, and a time of file creation, reading, updating, or deletion.

### Claim 5 (depends on 1)

The method of claim 1, wherein analyzing the file description metadata comprises identifying a first file on the at least one computing device as being anomalous based on the first file having the same filename and at least one of a different file extension and a different MIME type as a second file on the at least one computing device, wherein the second file has been identified as anomalous.

### Claim 6 (depends on 1)

The method of claim 1, wherein analyzing of file backup metadata of the plurality of computing devices to detect the first anomalous file backup activity event and the second anomalous file backup activity event involves applying a separate analysis model to each computing device of the plurality of computing devices, each of the separate analysis models based on employing one or more machine learning models, prior backup activity, or characteristics of a corresponding computing device of the plurality of computing devices.

### Claim 7

A system comprising:
one or more hardware processors; and
a memory storing instructions that, when executed by the one or more hardware processors, cause the system to perform operations comprising:
accessing file backup metadata of a plurality of computing devices;
analyzing the file backup metadata to detect a first anomalous file backup activity event and a second anomalous file backup activity event on at least one computing device of the plurality of computing devices, wherein each of the first and second anomalous file backup activity events are detected based on identifying a sudden change in addition of files and a sudden change in deletion of files since a most recent backup operation, and wherein the first and second anomalous file backup activity events include an associated detected time;
determining that the first anomalous file backup activity event and the second anomalous file backup activity event are correlated based on determining the associated detected time of the first anomalous file backup activity event and the associated detected time of the second anomalous file backup activity event are within a predetermined time period of each other;
accessing file description metadata for the at least one computing device of the plurality of computing devices;
analyzing the accessed file description metadata to identify anomalous files; and
determining that a ransomware attack or unauthorized encrypting of files has begun based on the determination that the first anomalous file backup activity event and the second anomalous file backup activity event are correlated and based on the identified anomalous files.

### Claim 8 (depends on 7)

The system of claim 7, wherein the operations further comprise:
analyzing the file backup metadata to detect a third anomalous file backup activity event at another computing device of the plurality of computing devices;
determining that the third anomalous file backup activity event is correlated with the first anomalous file backup activity event and the second anomalous file backup activity event;
accessing file description metadata for the another computing device;
analyzing the file description metadata for the another computing device to identify anomalous files at the another computing device; and
wherein the determination that a ransomware attack or unauthorized encrypting of files has begun is further based on the determination that the third anomalous file backup activity event is correlated with the first anomalous file backup activity event and the second anomalous file backup activity event and further based on the identified anomalous files at the another computing device.

### Claim 9 (depends on 7)

The system of claim 7, wherein the file description metadata comprises file extensions, wherein analyzing the file description metadata to identify anomalous files at the at least one computing device of the plurality of computing devices comprises determining file extensions of the anomalous files at the at least one computing device are different than file extensions of other files at the at least one computing device.

### Claim 10 (depends on 7)

The system of claim 7, wherein the file description metadata comprises at least one of a filename, a file MIME type, a file size, a file hash, and a time of file creation, reading, updating, or deletion.

### Claim 11

One or more non-transitory computer readable media encoding instructions which, when executed by one or more hardware processors, cause the one or more processors to perform operations comprising:
accessing file backup metadata on at least one computing device of the plurality of computing devices;
analyzing the file backup metadata to detect a first anomalous file backup activity event and a second anomalous file backup activity event on the at least one computing device, wherein each of the first and second anomalous file backup activity events are detected based on identifying a sudden change in addition of files and a sudden change in deletion of files since a most recent backup operation, and wherein the first and second anomalous file backup activity events include an associated detected time;
determining that the first anomalous file backup activity event and the second anomalous file backup activity event are correlated based on determining the associated detected time of the first anomalous file backup activity event and the associated detected time of the second anomalous file backup activity event are within a predetermined time period of each other;
accessing file description metadata for the at least one computing device of the plurality of computing devices;
analyzing the accessed file description metadata to identify anomalous files; and
determining that a ransomware attack or unauthorized encrypting of files has begun based on the determination that the first anomalous file backup activity event and the second anomalous file backup activity event are correlated and based on the identified anomalous files.

### Claim 12 (depends on 11)

The one or more non-transitory computer readable media of claim 11, wherein the operations further comprise:
analyzing the file backup metadata to detect a third anomalous file backup activity event at another computing device of the plurality of computing devices;
determining that the third anomalous file backup activity event is correlated with the first anomalous file backup activity event and the second anomalous file backup activity event;
accessing file description metadata for the another computing device;
analyzing the file description metadata for the another computing device to identify anomalous files at the another computing device; and
wherein the determination that a ransomware attack or unauthorized encrypting of files has begun is further based on the determination that the third anomalous file backup activity event is correlated with the first anomalous file backup activity event and the second anomalous file backup activity event and further based on the identified anomalous files at the another computing device.

### Claim 13 (depends on 11)

The one or more non-transitory computer readable media of claim 11, wherein the file description metadata comprises file extensions, wherein analyzing the file description metadata to identify anomalous files at the at least one computing device of the plurality of computing devices comprises determining file extensions of the anomalous files at the at least one computing device are different than file extensions of other files at the at least one computing device.

### Claim 14 (depends on 11)

The one or more non-transitory computer readable media of claim 11, wherein the file description metadata comprises at least one of a filename, a file MIME type, a file size, a file hash, and a time of file creation, reading, updating, or deletion.

### Claim 15 (depends on 11)

The one or more non-transitory computer readable media of claim 11, wherein analyzing the file description metadata comprises identifying a first file on the at least one computing device as being anomalous based on the first file having the same filename and at least one of a different file extension and a different MIME type as a second file on the at least one computing device, wherein the second file has been identified as anomalous.
