# US 2010/0169969 A1 · Functional patching/hooking detection and prevention

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

- Number: US 2010/0169969 A1
- Document ID: US20100169969A1
- Status: Published application
- Kind: A1
- Application number: 12/537,893
- Filed: 2009-08-07
- Published: 2010-07-01
- Earliest claimed: 2008-12-25
- Assignees: Trusteer Ltd.
- Inventors: Amit KLEIN; Oleg Izmerly; Shmuel Regev; Eldan Ben-Haim
- Web page: https://patentgrep.com/patent/US20100169969A1

## CPC

- G06F 21/57: Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
- G06F 9/328: {for runtime instruction patching}
- G06F 21/554: {involving event detection and direct action}
- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method for preventing malicious attacks on software, using the patching method, includes providing a database of legitimate and known patches, the database contains characteristic code paths of said legitimate patches. The method also includes detecting whether a patch is malicious by inspecting one or more characteristic paths of the patch and matching one or more code paths against the database of legitimate and known patches. An activity needed to prevent the malicious patch from performing undesired activities is then performed.

## Claims

### Claim 1

A method for preventing malicious attacks on software, using the patching method, comprising the steps of:
i) providing a database of legitimate and known patches, which database contains characteristic code paths of said legitimate patches;
ii) detecting whether a patch is malicious by inspecting one or more characteristic paths of said patch and matching said one or more code paths against said database of legitimate and known patches; and
iii) performing an activity needed to prevent said malicious patch from performing undesired activities.

### Claim 2 (depends on 1)

A method according to claim 1, wherein performing an activity needed to prevent said malicious patch from performing undesired activities comprises making changes to said malicious patch to prevent it from performing undesired activities, or deleting it.

### Claim 3 (depends on 1)

A method according to claim 1, wherein performing an activity needed to prevent said malicious patch from performing undesired activities comprises reporting the presence of the malicious path to a receiving entity.

### Claim 4 (depends on 3)

A method according to claim 3, wherein said receiving entity is selected from one or more of a remote software agent, a local software agent, or a user.

### Claim 5 (depends on 1)

A method according to claim 1, wherein the characteristic code path inspected includes the pointer to the function in the Export Address Table (EAT).

### Claim 6 (depends on 1)

A method according to claim 1, wherein the characteristic code path inspected includes the pointer to the function in the Import Address Table (IAT) of the currently loaded modules.

### Claim 7 (depends on 1)

A method according to claim 1, wherein the characteristic code path inspected includes the code of the function.

### Claim 8 (depends on 1)

A method according to claim 1, comprising providing in the database also information regarding where to look for the next patch.

### Claim 9 (depends on 1)

A method according to claim 1, comprising providing in the database also information on how to “linearize” the code being examined.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the process is repeated until no match is found in the database.

### Claim 11 (depends on 1)

A method according to claim 1, further comprising, when a malicious patch is detected, correcting the patch by making appropriate changes to the patch, or deleting the patch.

### Claim 12 (depends on 1)

The method according to claim 1, wherein the software is a browser.
