# US 2017/0255777 A1 · Methods and apparatus for identifying and removing malicious applications

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

- Number: US 2017/0255777 A1
- Document ID: US20170255777A1
- Status: Published application
- Kind: A1
- Application number: 15/600,001
- Filed: 2017-05-19
- Published: 2017-09-07
- Earliest claimed: 2012-05-09
- Assignees: SunStone Information Defense, Inc.
- Applicants: SunStone Information Defense, Inc.
- Inventors: David K. Ford
- Web page: https://patentgrep.com/patent/US20170255777A1

## 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/2105: Dual mode as a secondary aspect
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A system, method, and apparatus for identifying and removing malicious applications are disclosed. An example apparatus includes an executable application configured to collect data regarding processes operating on a client device during a time period. The executable application is also configured to purposefully access, during the time period, an application server using a web browser on the client device in an attempt to trigger a malicious application potentially located on the client device. The executable application is configured to transmit, after the time period, the collected data to an analysis server to determine whether the malicious application is located on the client device.

## Claims

### Claim 1

An apparatus comprising:
a client device including a processor and a memory, the client device being communicatively coupled to a network; and
an executable application including instructions stored in the memory, which when executed, cause the processor to:
collect data regarding processes operating on the client device during a time period,
purposefully access, during the time period, an application server via the network using a web browser on the client device in an attempt to trigger a malicious application potentially located on the client device, and
transmit, after the time period, the collected data to an analysis server to determine whether the malicious application is located on the client device.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the executable application includes further instructions, which when executed, cause the processor to select the application server based on the application server being a known intended target of the malicious application.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the executable application includes further instructions, which when executed, cause the processor to access the application server by at least one of performing a data operation with the application server, and carrying out a transaction with the application server.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the executable application includes further instructions, which when executed, cause the processor to:
place the client device into a quiescent state before or during the time period; and
take the client device out of the quiescent state after the time period or after the application server was accessed.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the executable application includes further instructions, which when executed, cause the processor to collect the data regarding the processes operating on the client device by receiving information from at least one of a task manager and a Windows Application Programmable Interface.

### Claim 6 (depends on 1)

The apparatus of claim 1, wherein the processes operating on the client device include related performance data metrics.

### Claim 7 (depends on 1)

The apparatus of claim 1, wherein the executable application includes further instructions, which when executed, cause the processor to:
start the time period for the collection of data before the access of the application server; and
end the time period after a specified number of minutes after the application server was accessed.

### Claim 8 (depends on 1)

The apparatus of claim 1, wherein the executable application includes further instructions, which when executed, cause the processor to:
receive a message from the analysis server indicative of files related to the malicious application; and
remove the malicious application from operation on the client device based on the received message.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein the executable application includes further instructions, which when executed, cause the processor to:
place the client device into a quiescent state before or during the time period; and
take the client device out of the quiescent state:
after receiving a second message, instead of the message, from the analysis server indicative that the malicious application is not present, or
after removing the malicious application from operation on the client device.

### Claim 10

A method comprising:
operating an executable application on a client device configured to:
place the client device into a quiescent state;
collect data regarding processes operating on the client device;
access an application server from the client device and perform at least one data operation; and
transmit the collected data to an analysis server;
analyzing the collected data to identify a malicious application by:
determining which processes on the client device were triggered after the application server was accessed by the executable application; and
comparing the determined processes to records of processes from a device similarly configured as the client device to identify processes associated with the malicious application;
determining files on the client device that are associated with the identified malicious application; and
based on the analysis of the collected data, transmitting instructions to the executable application on the client device causing the executable application to remove the malicious application from operation on the client device.

### Claim 11 (depends on 10)

The method of claim 10, wherein the executable application is configured to access the application server to stimulate the malicious application without input from a user of the client device.

### Claim 12 (depends on 10)

The method of claim 10, further comprising:
prior to operating the executable application, detecting at the application server that the malicious application is affecting communications between the client device and the application server, the application server being communicatively coupled to the client via a network; and
transmitting the executable application from the application server to the client device.

### Claim 13 (depends on 10)

The method of claim 10, further comprising:
prior to operating the executable application, detecting at a second application server that the malicious application is affecting communications between the client device and the second application server, the second application server being different from the application server; and
transmitting an instruction from the second application server to the client device causing the executable application to begin operating.

### Claim 14 (depends on 10)

The method of claim 10, further comprising responsive to removing the malicious application placing the client device into a normal operating state and deactivating the executable application.

### Claim 15 (depends on 10)

The method of claim 10, wherein determining the files on the client device that are associated with the identified malicious application includes remotely accessing the client device and scanning a memory of the client device for files corresponding to processes of the identified malicious application.

### Claim 16

A machine-accessible device having instructions stored thereon that, when executed, cause a machine to at least:
collect data regarding processes operating on a client device;
purposefully access an application server using a web browser on the client device in an attempt to trigger a malicious application potentially located on the client device;
transmit the collected data to an analysis server to enable determination as to whether the malicious application is located on the client device;
receive a message from the analysis server indicative of the malicious application; and
remove the malicious application from operation on the client device based on the received message.

### Claim 17 (depends on 16)

The machine-accessible device of claim 16, further comprising instructions stored thereon that are configured when executed to cause the machine to:
store first information identifying the application server that was purposefully accessed;
store second information identifying a time the application server was accessed; and
transmit the first information and the second information to the analysis server to enable determination as to whether the malicious application is located on the client device.

### Claim 18 (depends on 16)

The machine-accessible device of claim 16, further comprising instructions stored thereon that are configured when executed to cause the machine to:
collect second data regarding second processes operating on the client device after the step of removing the malicious application from operation;
purposefully accessing at least one of the application server and a second application server using the web browser on the client device in an attempt to trigger the malicious application potentially located on the client device;
transmit the second collected data to the analysis server to enable determination as to whether the malicious application is still located on the client device.

### Claim 19 (depends on 18)

The machine-accessible device of claim 18, further comprising instructions stored thereon that are configured when executed to cause the machine to:
place the client device into a quiescent state before collecting the data regarding the processes operating on the client device; and
take the client device out of the quiescent state after receiving a second message from the analysis server indicative that the malicious application is not present.

### Claim 20 (depends on 19)

The machine-accessible device of claim 19, where in the second message is received from the analysis server after transmitting the second collected data.
