# US 2026/0087137 A1 · System and method for detecting exploit including shellcode

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

- Number: US 2026/0087137 A1
- Document ID: US20260087137A1
- Status: Published application
- Kind: A1
- Application number: 19/407,495
- Filed: 2025-12-03
- Published: 2026-03-26
- Earliest claimed: 2022-01-28
- Assignees: Palo Alto Networks, Inc.
- Applicants: Palo Alto Networks, Inc.
- Inventors: Tao Yan; Jin Chen; Bo Qu; Jiangxia Liu; Edouard Bochin; Royce Lu
- Web page: https://patentgrep.com/patent/US20260087137A1

## CPC

- G06F 21/564: {by virus signature recognition}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 21/53: by executing in a restricted environment, e.g. sandbox or secure virtual machine
- G06F 21/568: {eliminating virus, restoring damaged files}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Detection of an exploit including shellcode is disclosed. Memory blocks are monitored during dynamic analysis of a sample to identify a memory block including suspicious shellcode. The memory block is dumped in memory to identify a candidate shellcode entry point associated with the suspicious shellcode. The suspicious shellcode is executed based on the candidate shellcode entry point to determine whether the suspicious shellcode is malicious. A verdict is generated regarding the sample based on results of executing the suspicious shellcode.

## Claims

### Claim 1

A system, comprising:
a processor configured to:
monitor memory blocks during dynamic analysis of a sample to identify a memory block including suspicious shellcode;
dump the memory block in memory to identify a candidate shellcode entry point associated with the suspicious shellcode;
execute, based on the candidate shellcode entry point, the suspicious shellcode to determine whether the suspicious shellcode is malicious, comprising to:
execute, based on the candidate shellcode entry point, the suspicious shellcode using a CPU emulator; and
generate a verdict regarding the sample based on results of executing the suspicious shellcode; and
a memory coupled to the processor and configured to provide the processor with instructions.

### Claim 2 (depends on 1)

The system of claim 1, wherein the monitoring of the memory blocks during the dynamic analysis of the sample to identify the memory block including the suspicious shellcode comprises to:
hook a memory attribute change function associated with a memory block to determine whether the memory attribute change function has been called and a corresponding parameter has been provided to the memory attribute change function; and
in response to a determination that the memory attribute change function has been called and the corresponding parameter has been provided to the memory attribute change function, determine that the memory block includes suspicious shellcode.

### Claim 3 (depends on 1)

The system of claim 1, wherein the monitoring of the memory blocks during the dynamic analysis of the sample to identify the memory block including the suspicious shellcode comprises to:
perform an offline scanning of process memory to determine whether the memory blocks have a specific memory attribute; and
in response to a determination that the memory block has the specific memory attribute, determine that the memory block includes the suspicious shellcode.

### Claim 4 (depends on 1)

The system of claim 1, wherein the dumping of the memory block in the memory to identify the candidate shellcode entry point associated with the suspicious shellcode comprises to:
identify a specific assembly code pattern or a specific data structure in the memory block including the suspicious shellcode; and
determine the candidate shellcode entry point based on the specific assembly code pattern or the specific data structure.

### Claim 5 (depends on 1)

The system of claim 1, wherein the executing of the suspicious shellcode further comprises to:
execute, based on the candidate shellcode entry point, the suspicious shellcode using a full system emulator.

### Claim 6 (depends on 5)

The system of claim 5, wherein the executing of the suspicious shellcode using the full system emulator comprises to:
execute the suspicious shellcode in the memory inside an operating system running in the full system emulator;
monitor hooked application programming interface (API) functions to determine whether the suspicious shellcode calls a hooked API function; and
in response to a determination that the suspicious shellcode calls the hooked API function, determine that the suspicious shellcode is malicious.

### Claim 7 (depends on 1)

The system of claim 1, wherein the executing of the suspicious shellcode using the CPU emulator comprises to:
emulate execution of the suspicious shellcode using the CPU emulator;
determine whether assembly instructions associated with the emulated execution of the suspicious shellcode matches a predetermined shellcode pattern; and
in response to a determination that the assembly instructions associated with the emulated execution of the suspicious shellcode matches the predetermined shellcode pattern, determine that the suspicious shellcode is malicious.

### Claim 8 (depends on 1)

The system of claim 1, wherein the processor is further configured to:
in response to a determination that the verdict indicates that the sample is malicious, generate a signature for the sample.

### Claim 9 (depends on 1)

The system of claim 1, wherein the processor is further configured to:
in response to a determination that the verdict indicates that the sample is malicious:
generate a signature for the sample; and
distribute the signature to a firewall.

### Claim 10

A method, comprising:
monitoring, using a processor, memory blocks during dynamic analysis of a sample to identify a memory block including suspicious shellcode;
dumping, using the processor, the memory block in memory to identify a candidate shellcode entry point associated with the suspicious shellcode;
executing, based on the candidate shellcode entry point, the suspicious shellcode to determine whether the suspicious shellcode is malicious using the processor, comprising:
executing, based on the candidate shellcode entry point, the suspicious shellcode using a CPU emulator; and
generating, using the processor, a verdict regarding the sample based on results of executing the suspicious shellcode.

### Claim 11 (depends on 10)

The method of claim 10, wherein the monitoring of the memory blocks during the dynamic analysis of the sample to identify the memory block including the suspicious shellcode comprises:
hooking a memory attribute change function associated with a memory block to determine whether the memory attribute change function has been called and a corresponding parameter has been provided to the memory attribute change function; and
in response to a determination that the memory attribute change function has been called and the corresponding parameter has been provided to the memory attribute change function, determining that the memory block includes suspicious shellcode.

### Claim 12 (depends on 10)

The method of claim 10, wherein the monitoring of the memory blocks during the dynamic analysis of the sample to identify the memory block including the suspicious shellcode comprises:
performing an offline scanning of process memory to determine whether the memory blocks have a specific memory attribute; and
in response to a determination that the memory block has the specific memory attribute, determining that the memory block includes the suspicious shellcode.

### Claim 13 (depends on 10)

The method of claim 10, wherein the dumping of the memory block in the memory to identify the candidate shellcode entry point associated with the suspicious shellcode comprises:
identifying a specific assembly code pattern or a specific data structure in the memory block including the suspicious shellcode; and
determining the candidate shellcode entry point based on the specific assembly code pattern or the specific data structure.

### Claim 14 (depends on 10)

The method of claim 10, wherein the executing of the suspicious shellcode comprises:
executing, based on the candidate shellcode entry point, the suspicious shellcode using a full system emulator.

### Claim 15 (depends on 14)

The method of claim 14, wherein the executing of the suspicious shellcode using the full system emulator comprises:
executing the suspicious shellcode in the memory inside an operating system running in the full system emulator;
monitoring hooked application programming interface (API) functions to determine whether the suspicious shellcode calls a hooked API function; and
in response to a determination that the suspicious shellcode calls the hooked API function, determining that the suspicious shellcode is malicious.

### Claim 16 (depends on 10)

The method of claim 10, wherein the executing of the suspicious shellcode using the CPU emulator comprises:
emulating execution of the suspicious shellcode using the CPU emulator;
determining whether assembly instructions associated with the emulated execution of the suspicious shellcode matches a predetermined shellcode pattern; and
in response to a determination that the assembly instructions associated with the emulated execution of the suspicious shellcode matches the predetermined shellcode pattern, determining that the suspicious shellcode is malicious.

### Claim 17 (depends on 10)

The method of claim 10, further comprising:
in response to a determination that the verdict indicates that the sample is malicious, generating a signature for the sample.

### Claim 18 (depends on 10)

The method of claim 10, further comprising:
in response to a determination that the verdict indicates that the sample is malicious:
generating a signature for the sample; and
distributing the signature to a firewall.

### Claim 19

A system, comprising:
a processor configured to:
means for monitoring memory blocks during dynamic analysis of a sample to identify a memory block including suspicious shellcode;
means for dumping the memory block in memory to identify a candidate shellcode entry point associated with the suspicious shellcode;
execute, based on the candidate shellcode entry point, the suspicious shellcode to determine whether the suspicious shellcode is malicious, comprising to:
execute, based on the candidate shellcode entry point, the suspicious shellcode using a CPU emulator; and
means for generating a verdict regarding the sample based on results of executing the suspicious shellcode; and
a memory coupled to the processor and configured to provide the processor with instructions.

### Claim 20 (depends on 19)

The system of claim 19, wherein the executing of the suspicious shellcode further comprises to:
execute, based on the candidate shellcode entry point, the suspicious shellcode using a full system emulator.
