# US 2022/0035920 A1 · Systems and methods for automatically generating malware countermeasures

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

- Number: US 2022/0035920 A1
- Document ID: US20220035920A1
- Status: Published application
- Kind: A1
- Application number: 16/944,079
- Filed: 2020-07-30
- Published: 2022-02-03
- Earliest claimed: 2020-07-30
- Assignees: Versa Networks, Inc.
- Applicants: Versa Networks, Inc.
- Inventors: Winny M. THOMAS
- Web page: https://patentgrep.com/patent/US20220035920A1

## CPC

- G06F 21/568: {eliminating virus, restoring damaged files}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- 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

Malware can be automatically detected and countermeasures automatically generated. A virtual machine (VM) is run with an operating system configured with a monitoring subsystem. The monitoring subsystem is configured to generate event data based on events occurring on the virtual machine. The monitoring subsystem can run within the operating system kernel. Kernel drivers can register to receive specific events. The events are therefore sent to the drivers, which can send them to a classifier. The classifier can detect malware based on the events. When a sample is run on the VM, the classifier can detect malware in the sample. While running the sample, event data is collected. A countermeasure compiler can generate a countermeasure to the malware, the countermeasure based on the event data.

## Claims

### Claim 1

A method comprising:
running a virtual machine with an operating system configured with a monitoring subsystem, the monitoring subsystem configured to generate event data based on a plurality of events occurring on the virtual machine;
running a classifier configured to detect a malware based on the plurality of events;
running a sample on the virtual machine, the classifier detecting the malware in the sample; and
running a countermeasure compiler that generates a countermeasure to the malware, the countermeasure based on the event data.

### Claim 2 (depends on 1)

The method of claim 1 wherein the monitoring subsystem is run within a kernel of the operating system. 3. The method of claim 1 wherein detecting the malware triggers generating the countermeasure.

### Claim 4 (depends on 1)

The method of claim 1 wherein the countermeasure compiler is configured to generate a resource data section and wherein the countermeasure includes a precompiled template populated with the resource data section.

### Claim 5 (depends on 1)

The method of claim 1, the classifier configured to:
detect the malware based on the sample modifying a tripwire file monitored by the monitoring subsystem, and
detect the malware based on the sample modifying a system file monitored by the monitoring subsystem.

### Claim 6 (depends on 1)

The method of claim 1, the classifier configured to detect the malware based on the sample terminating a process monitored by the monitoring subsystem and that is not associated with the sample.

### Claim 7 (depends on 1)

The method of claim 1, the monitoring subsystem configured to monitor a process, and the classifier configured to:
detect the malware based on a type of access to the process requested by the sample, and
detect the malware based on an identity of the process accessed by the sample.

### Claim 8 (depends on 1)

The method of claim 1, the monitoring subsystem configured to monitor an operating system registry, and the classifier configured to:
detect the malware based on the sample modifying or deleting a registry entry that the sample did not create.

### Claim 9 (depends on 1)

The method of claim 1, wherein the countermeasure is configured to:
run on a computer, and
detect the malware on the computer.

### Claim 10 (depends on 1)

The method of claim 1, wherein the countermeasure is configured to:
run on a computer, and
remove the malware from the computer.

### Claim 11 (depends on 1)

The method of claim 1, wherein the countermeasure is configured to:
run on a computer, and
prevent the computer from running a malware process.

### Claim 12 (depends on 1)

The method of claim 1
wherein detecting the malware triggers generating the countermeasure;
wherein the monitoring subsystem is configured to:
run within a kernel of the operating system,
monitor a first process not associated with the sample,
monitor a second process,
monitor a tripwire file,
monitor a system file, and
to monitor an operating system registry;
wherein the classifier is configured to:
run within the kernel of the operating system,
use an event data object in transient memory and based on the plurality of events to detect the malware based on at least two of the plurality of events,
detect the malware based on the sample modifying the tripwire file,
detect the malware based on the sample modifying the system file,
detect the malware based on the sample terminating the first process,
detect the malware based on a type of access to the second process requested by the sample,
detect the malware based on an identity of the second process accessed by the sample, and
detect the malware based on the sample modifying or deleting a registry entry that the sample did not create;
wherein the countermeasure compiler is configured to generate a resource data section by compiling an analysis log file comprising the event data, the analysis log file not visible to the virtual machine; and
wherein the countermeasure includes a precompiled template populated with the resource data section and is configured to:
run on a computer,
detect the malware on the computer,
remove the malware from the computer, and
prevent the computer from running a malware process.

### Claim 13

A system comprising:
a virtual machine running an operating system, the virtual machine configured to run a sample comprising a malware;
a monitoring subsystem running on the virtual machine and configured to generate event data based on a plurality of events occurring on the virtual machine;
a classifier configured to detect the malware based on the plurality of events; and
a countermeasure compiler configured to compile an analysis log file including the event data to generate a countermeasure to the malware.

### Claim 14 (depends on 13)

The system of claim 13 wherein the classifier is configured to use an event data object in transient memory and based on the plurality of events to detect the malware based on at least two of the plurality of events. 15. The system of claim 13 wherein the monitoring subsystem and the classifier are run within a kernel of the operating system.

### Claim 16 (depends on 13)

The system of claim 13 wherein generating the countermeasure is triggered by detecting the malware.

### Claim 17 (depends on 13)

The system of claim 13 wherein the countermeasure is configured to:
run on a computer,
detect the malware on the computer,
remove the malware from the computer, and
prevent the computer from running a malware process.

### Claim 18

A non-transitory computer readable medium storing computer readable instructions, that when executed on one or more processors, implements a method comprising:
running a virtual machine with an operating system configured with a monitoring subsystem, the monitoring subsystem configured to generate event data based on a plurality of events occurring on the virtual machine;
running a classifier configured to detect a malware based on the plurality of events;
running a sample on the virtual machine, the classifier detecting the malware in the sample; and
running a countermeasure compiler that generates a countermeasure to the malware, the countermeasure based on the event data.

### Claim 19 (depends on 18)

The non-transitory computer readable medium storing computer readable instructions of claim 18,
wherein the monitoring subsystem is configured to:
run within a kernel of the operating system,
monitor a first process not associated with the sample,
monitor a second process,
monitor a tripwire file, and
monitor a system file; and
wherein the classifier is configured to:
detect the malware based on the sample modifying the tripwire file,
detect the malware based on the sample modifying the system file,
detect the malware based on the sample terminating the first process,
detect the malware based on a type of access to the second process requested by the sample, and
detect the malware based on an identity of the second process accessed by the sample.

### Claim 20 (depends on 18)

The non-transitory computer readable medium storing computer readable instructions of claim 18, wherein the countermeasure is stored on a second non-transitory computer readable medium storing additional computer readable instructions, that when executed by a computer, implement a countermeasure method comprising:
detecting the malware on the computer, and
removing the malware from the computer.
