# US 2012/0255013 A1 · System and method for below-operating system modification of malicious code on an electronic device

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

- Number: US 2012/0255013 A1
- Document ID: US20120255013A1
- Status: Published application
- Kind: A1
- Application number: 13/074,925
- Filed: 2011-03-29
- Published: 2012-10-04
- Earliest claimed: 2011-03-29
- Assignees: McAfee, Inc.
- Inventors: Ahmed Said Sallam
- Web page: https://patentgrep.com/patent/US20120255013A1

## CPC

- G06F 21/564: {by virus signature recognition}
- G06F 21/554: {involving event detection and direct action}
- G06F 21/568: {eliminating virus, restoring damaged files}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system for securing an electronic device, may include a memory, a processor, one or more operating systems residing in the memory for execution by the processor; and a security agent configured to execute on the electronic device at a level below all of the operating systems of the electronic device accessing the memory. The security agent may be further configured to detect presence of malicious code, and in response to detecting presence of the malicious code, modify the malicious code.

## Claims

### Claim 1

A method for securing an electronic device, comprising:
detecting, at a level below all of the operating systems of the electronic device accessing a memory or a storage of the electronic device, presence of malicious code; and
in response to detecting the presence of malicious code, modifying, at a level below all of the operating systems of the electronic device accessing the memory or the storage of the electronic device, the malicious code.

### Claim 2 (depends on 1)

The method of claim 1, wherein modifying the malicious code comprises modifying the malicious code as embodied in a memory of the electronic device.

### Claim 3 (depends on 2)

The method of claim 2, wherein modifying the malicious code as embodied in the memory of the electronic device comprises at least one of:
modifying the malicious code such that an entity including the malicious code self-terminates; and
modifying the malicious code such that the modified code transfers execution to trusted code configured to neutralize the malicious code.

### Claim 4 (depends on 1)

The method of claim 1, wherein modifying the malicious code includes modifying the malicious code as embodied in storage of the electronic device.

### Claim 5 (depends on 4)

The method of claim 4, wherein modifying the malicious code as embodied in storage of the electronic device comprises:
referencing collected information regarding a relationship of content stored in the memory to corresponding content stored in the storage; and
modifying content in a location of storage corresponding to a location of the memory having the malicious code.

### Claim 6 (depends on 1)

The method of claim 1, wherein modifying the malicious code includes modifying the malicious code's access to the memory or other resources of the electronic device to deny the malicious code any access to the memory or other resources of the electronic device.

### Claim 7 (depends on 1)

The method of claim 1, further comprising identifying other portions of memory potentially having malicious code based on the physical memory address of the detected malicious code.

### Claim 8

A system for securing an electronic device, comprising:
a memory;
a processor;
one or more operating systems residing in the memory for execution by the processor;
a security agent configured to execute on the electronic device at a level below all of the operating systems of the electronic device accessing the memory, and further configured to:
detect presence of malicious code; and
in response to detecting presence of the malicious code, modify the malicious code.

### Claim 9 (depends on 8)

The system of claim 8, wherein modifying the malicious code comprises modifying the malicious code as embodied in the memory.

### Claim 10 (depends on 9)

The system of claim 9, wherein modifying the malicious code as embodied in the memory comprises at least one of:
modifying the malicious code such that an entity including the malicious code self-terminates; and
modifying the malicious code such that the modified code transfers execution to trusted code configured to neutralize the malicious code.

### Claim 11 (depends on 8)

The system of claim 8, wherein modifying the malicious code includes modifying the malicious code as embodied in storage of the electronic device.

### Claim 12 (depends on 11)

The system of claim 11, wherein modifying the malicious code as embodied in storage of the electronic device comprises:
referencing collected information regarding a relationship of content stored in the memory to corresponding content stored in the storage; and
modifying content in a location of storage corresponding to a location of the memory having the malicious code.

### Claim 13 (depends on 8)

The system of claim 8, wherein modifying the malicious code includes modifying the malicious code's access to the memory or other resources of the electronic device to deny the malicious code any access to the memory or other resources of the electronic device.

### Claim 14 (depends on 8)

The system of claim 8, the security agent further configured to identify other portions of the memory potentially having malicious code based on the physical memory address of the detected malicious code.

### Claim 15

An article of manufacture, comprising:
a computer readable medium;
computer-executable instructions carried on the computer readable medium, the instructions readable by a processor, the instructions, when read and executed, for causing the processor to, at a level below all of the operating systems of an electronic device accessing a memory or storage of the electronic device:
detect presence of malicious code in the memory or storage of electronic device; and
in response to detecting presence of the malicious code, modifying the malicious code.

### Claim 16 (depends on 15)

The article of claim 15, wherein modifying the malicious code comprises modifying the malicious code as embodied in a memory of the electronic device.

### Claim 17 (depends on 16)

The article of claim 16, wherein modifying the malicious code as embodied in the memory of the electronic device comprises at least one of:
modifying the malicious code such that an entity including the malicious code self-terminates; and
modifying the malicious code such that the modified code transfers execution to trusted code configured to neutralize the malicious code.

### Claim 18 (depends on 15)

The article of claim 15, wherein modifying the malicious code includes modifying the malicious code as embodied in storage of the electronic device.

### Claim 19 (depends on 18)

The article of claim 18, wherein modifying the malicious code as embodied in storage of the electronic device comprises:
referencing collected information regarding a relationship of content stored in the memory to corresponding content stored in the storage; and
modifying content in a location of storage corresponding to a location of the memory having the malicious code.

### Claim 20 (depends on 15)

The article of claim 15, wherein modifying the malicious code includes modifying the malicious code's access to the memory or other resources of the electronic device to deny the malicious code any access to the memory or other resources of the electronic device.

### Claim 21 (depends on 15)

The system of claim 15, wherein the processor is further caused to identify other portions of the memory potentially having malicious code based on the physical memory address of the detected malicious code.
