# US 2016/0253500 A1 · System and method to mitigate malware

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

- Number: US 2016/0253500 A1
- Document ID: US20160253500A1
- Status: Published application
- Kind: A1
- Application number: 14/751,935
- Filed: 2015-06-26
- Published: 2016-09-01
- Earliest claimed: 2015-02-26
- Assignees: McAfee, Inc.
- Applicants: McAfee, Inc.
- Inventors: Christoph Alme; Slawa Hahn; Stefan Finke
- Web page: https://patentgrep.com/patent/US20160253500A1

## CPC

- G06F 21/563: {by source code analysis}
- G06F 16/2246: {Trees, e.g. B+trees}
- G06F 21/552: {involving long-term monitoring or reporting}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Particular embodiments described herein provide for an electronic device that can be configured to receive script data, determine a checksum tree for the script data, compare each checksum of the checksum tree to one or more subtree checksums, and assign one or more classifications to the script data. In one example, the checksum tree is an abstract syntax tree.

## Claims

### Claim 1

At least one machine readable medium comprising one or more instructions that when executed by a processor, cause the machine readable medium to:
receive script data;
determine a checksum tree for the script data;
compare each checksum of the checksum tree to one or more subtree checksums; and
assign one or more classifications to the script data.

### Claim 2 (depends on 1)

The at least one machine readable medium of claim 1, wherein the checksum tree is calculated on an abstract syntax tree.

### Claim 3 (depends on 1)

The at least one machine readable medium of claim 1, wherein each checksum in the subtree checksums is a prevalent malware or benign checksum.

### Claim 4 (depends on 1)

The at least one machine readable medium of claim 1, wherein the classification is based on a subtree of the checksum tree that matches a checksum in the subtree checksums.

### Claim 5 (depends on 1)

The at least one machine readable medium of claim 1, wherein a percentage is assigned to the classification.

### Claim 6 (depends on 1)

The at least one machine readable medium of claim 1, wherein one or more checksums of the checksum tree is a fuzzy checksum.

### Claim 7 (depends on 1)

The at least one machine readable medium of claim 1, further comprising one or more instructions that when executed by the at least one processor, cause the machine readable medium to:
serialize the checksum tree into a feature vector.

### Claim 8 (depends on 7)

The at least one machine readable medium of claim 7, further comprising one or more instructions that when executed by the at least one processor, cause the machine readable medium to:
communicate the feature vector to a network element for further analysis.

### Claim 9

An apparatus comprising:
a tree generation module configured to:
receive script data;
determine a checksum tree for the script data; and
a detection module configured to:
compare each checksum of the checksum tree to one or more subtree checksums; and
assign one or more classifications to the script data.

### Claim 10 (depends on 9)

The apparatus of claim 9, wherein the checksum tree is calculated on an abstract syntax tree.

### Claim 11 (depends on 9)

The apparatus of claim 9, wherein each checksum in the subtree checksums is a prevalent malware or benign checksum.

### Claim 12 (depends on 9)

The apparatus of claim 9, wherein the classification is based on a subtree of the checksum tree that matches a checksum in the subtree checksums.

### Claim 13 (depends on 9)

The apparatus of claim 9, wherein a percentage is assigned to the classification.

### Claim 14 (depends on 9)

The apparatus of claim 9, wherein one or more checksums of the checksum tree is a fuzzy checksum.

### Claim 15 (depends on 9)

The apparatus of claim 9, wherein the detection module is further configured to:
serialize the checksum tree into a feature vector.

### Claim 16 (depends on 15)

The apparatus of claim 15, wherein the detection module is further configured to:
communicate the feature vector to a network element for further analysis.

### Claim 17

A method comprising:
receiving script data;
determining a checksum tree for the script data;
comparing each checksum of the checksum tree to one or more subtree checksums; and
assigning one or more classifications to the script data.

### Claim 18 (depends on 17)

The method of claim 17, wherein the checksum tree is calculated on an abstract syntax tree.

### Claim 19 (depends on 17)

The method of claim 17, wherein each checksum in the subtree checksums is a prevalent malware or benign checksum.

### Claim 20 (depends on 17)

The method of claim 17, wherein the classification is based on a subtree of the checksum tree that matches a checksum in the subtree checksums.

### Claim 21 (depends on 17)

The method of claim 17, wherein a percentage is assigned to the classification.

### Claim 22 (depends on 17)

The method of claim 17, wherein one or more checksums of the checksum tree is a fuzzy checksum.

### Claim 23 (depends on 17)

The method of claim 17, further comprising:
serializing the checksum tree into a feature vector; and
communicating the feature vector to a network element for further analysis.

### Claim 24

A system for mitigating malware, the system comprising:
a tree generation module configured to:
receive script data;
determine a checksum tree for the script data; and
a detection module configured to:
compare each checksum of the checksum tree to one or more subtree checksums; and
assign one or more classifications to the script data.

### Claim 25 (depends on 24)

The system of claim 24, wherein the classification is based on a subtree of the checksum tree that matches a checksum in the subtree checksums.
