# US 2021/0342445 A1 · Systems and Methods for Identifying Malware Injected into a Memory of a Computing Device

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

- Number: US 2021/0342445 A1
- Document ID: US20210342445A1
- Status: Published application
- Kind: A1
- Application number: 17/373,001
- Filed: 2021-07-12
- Published: 2021-11-04
- Earliest claimed: 2017-07-13
- Assignees: Endgame, Inc.
- Applicants: Endgame, Inc.
- Inventors: Joseph W. Desimone
- Web page: https://patentgrep.com/patent/US20210342445A1

## CPC

- G06F 21/563: {by source code analysis}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 21/577: {Assessing vulnerabilities and evaluating computer system security}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

In the embodiments described herein, a malicious code detection module identifies potentially malicious instructions in memory of a computing device. The malicious code detection module examines the call stack for each thread running within the operating system of the computing device. Within each call stack, the malicious code detection module identifies the originating module for each stack frame and determines whether the originating module is backed by an image on disk. If an originating module is not backed by an image on disk, the thread containing that originating module is flagged as potentially malicious, execution of the thread optionally is suspended, and an alert is generated for the user or administrator.

## Claims

### Claim 1

A method of identifying malware in a computing device comprising a processor executing an operating system and a malicious code detection module, memory, and a non-volatile storage device, the method comprising:
identifying, by the malicious code detection module, a call stack for a thread of execution within the operating system that includes an originating module and an attribute table;
determining, by the malicious code detection module, the originating module that initiated a stack frame in the call stack, wherein the determining step is performed for additional stack frames in the call stack until a threshold or event is reached; and
generating an alert, by the malicious code detection module, when the attribute table associated with the originating module indicates that the originating module is not backed by a file stored in the non-volatile storage device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the malicious code detection module is part of a kernel of the operating system.

### Claim 3 (depends on 1)

The method of claim 1, wherein the malicious code detection module is not part of the operating system.

### Claim 4 (depends on 1)

The method of claim 1, further comprising assigning, by the malicious code detection module, a unique identifier to the call stack.

### Claim 5 (depends on 1)

The method of claim 1, further comprising suspending the thread until a user or an administrator expressly instructs the computing device to proceed with execution of the thread.

### Claim 6 (depends on 1)

The method of claim 1, wherein the malicious code detection module is outside of the operating system that is given a special privilege by the operating system.

### Claim 7 (depends on 6)

The method of claim 6, wherein the special privilege comprises an ability to access attribute information that indicates whether an item is backed by a file stored in the non-volatile storage device.

### Claim 8 (depends on 6)

The method of claim 6, wherein the special privilege comprises an ability to suspend execution of a thread.

### Claim 9 (depends on 1)

The method of claim 1, wherein the alert comprises at least one of a message displayed on a computing device of a user or administrator, an audible sound generated by the computing device, an email, a SMS message, a MMS message, and any type of message to be sent to a computing device of a user or administrator.

### Claim 10

A method of identifying malicious code in a computing device comprising a processor executing an operating system and a malicious code detection module, memory, and a non-volatile storage device, the method comprising:
identifying, by the malicious code detection module, a call stack for a thread of execution within the operating system that includes an originating module and an attribute table;
determining, by the malicious code detection module, the originating module that initiated a stack frame in the call stack, wherein the determining step is performed for additional stack frames in the call stack until a threshold or event is reached; and
suspending, by the malicious code detection module, a thread of execution containing the originating module when the attribute table associated with the originating module indicates that the originating module is not backed by a file stored in the non-volatile storage device.

### Claim 11 (depends on 10)

The method of claim 10, wherein the malicious code detection module is part of a kernel of the operating system.

### Claim 12 (depends on 10)

The method of claim 10, wherein the malicious code detection module is not part of the operating system.

### Claim 13 (depends on 10)

The method of claim 10, further comprising assigning, by the malicious code detection module, a unique identifier to the call stack.

### Claim 14 (depends on 10)

The method of claim 10, wherein the malicious code detection module is outside of the operating system that is given a special privilege by the operating system.

### Claim 15 (depends on 14)

The method of claim 14, wherein the special privilege comprises an ability to access attribute information that indicates whether an item is backed by a file stored in the non-volatile storage device.

### Claim 16 (depends on 14)

The method of claim 14, wherein the special privilege comprises an ability to suspend execution of a thread.

### Claim 17

A computing device comprising: a processor executing an operating system and a malicious code detection module, memory, and a non-volatile storage device, wherein the malicious code detection module comprises instructions for:
identifying a call stack for a thread of execution that includes an originating module and an attribute table within the operating system;
determining the originating module that initiated a stack frame in the call stack, wherein the malicious code detection module further comprises instructions for performing the determining step for additional stack frames in the call stack until a threshold or event is reached; and
generating an alert if the attribute table associated with the originating module indicates that the originating module is not backed by a file stored in the non-volatile storage device.

### Claim 18 (depends on 17)

The device of claim 17, wherein the malicious code detection module is part of a kernel of the operating system.

### Claim 19 (depends on 17)

The device of claim 17, wherein the malicious code detection module is not part of the operating system.

### Claim 20 (depends on 17)

The device of claim 17, wherein the malicious code detection module further comprises instructions for suspending a thread of execution containing the originating module if the originating module is not backed by a file stored in the non-volatile storage device.

### Claim 21 (depends on 17)

The device of claim 17, wherein the malicious code detection module further comprises instructions for enumerating the call stack and the additional call stacks.
