# US 2019/0243973 A1 · System and method of termination of a functionally-limited application interrelated with a website and started without installation

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

- Number: US 2019/0243973 A1
- Document ID: US20190243973A1
- Status: Published application
- Kind: A1
- Application number: 15/960,956
- Filed: 2018-04-24
- Published: 2019-08-08
- Earliest claimed: 2018-02-06
- Assignees: AO Kaspersky Lab
- Applicants: Ao Kaspersky Lab
- Inventors: Victor V. Yablokov; Anton S. Samoylov; Alexander Y. Shindin
- Web page: https://patentgrep.com/patent/US20190243973A1

## CPC

- G06F 21/566: {Dynamic detection, i.e. detection performed at run-time, e.g. emulation, suspicious activities}
- G06F 21/554: {involving event detection and direct action}
- G06F 21/567: {using dedicated hardware}
- G06F 2221/033: Test or assess software
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Systems and methods for limiting applications launched without installation for the presence of malicious code. Applications launched without installation and which contain malicious code can be stopped or paused. Relationships between a fully-functional website-related application requiring installation and a functionally-restricted application launched without installation can be used to determine malicious code.

## Claims

### Claim 1

A system for detecting malicious code for a functionally-restricted website-related application launched without installation on a mobile device, the system comprising:
a computing platform including computing hardware of at least one processor and memory operably coupled to the at least one processor;
instructions that, when executed on the computing platform, cause the computing platform to implement:
a detection tool configured to—
detect activity of an operating system (OS) service related to the functionally-restricted website-related application launched without installation, and
determine at least one parameter of the functionally-restricted website-related application launched without installation;
a determination tool configured to—
receive the at least one parameter of the functionally-restricted website-related application launched without installation from the detection tool, and
determine a corresponding fully-functional application requiring installation based on the at least one parameter of the functionally-restricted website-related application launched without installation;
a check tool configured to—
receive information about the corresponding fully-functional application requiring installation from the determination tool,
check for malicious code in the corresponding fully-functional application requiring installation from the determination tool based on the information received from the determination tool, and
stop the launch of the functionally-restricted website-related application when the check for malicious code identifies malicious code.

### Claim 2 (depends on 1)

The system of claim 1, wherein detecting activity includes detecting an event showing a change in a system display.

### Claim 3 (depends on 2)

The system of claim 2, wherein determining the at least one parameter includes checking a name of the detected event using a URL_view or App_name field.

### Claim 4 (depends on 1)

The system of claim 1, wherein the at least one parameter of the functionally-restricted website-related application launched without installation is at least one of a filename of a file storing resources for the functionally-restricted website-related application launched without installation, a URL of the website related to the functionally-restricted website-related application launched without installation, or a filename of a container file of the functionally-restricted website-related application launched without installation.

### Claim 5 (depends on 1)

The system of claim 1, wherein the detection tool is further configured to suspend launch of the functionally-restricted website-related application launched without installation.

### Claim 6 (depends on 5)

The system of claim 5, wherein the detection tool suspends launch of the functionally-restricted website-related application launched without installation by simulating user selection of a home key on the mobile device.

### Claim 7 (depends on 1)

The system of claim 1, wherein determining the corresponding fully-functional application requiring installation includes analyzing an assetlinks.json file of the website related to the functionally-restricted website-related application launched without installation by:
searching the assetlinks.json file for all container file names related to the website; and
accessing a container file body and files of all versions of the corresponding fully-functional application requiring installation in an applications database by at least one of the container file names.

### Claim 8 (depends on 1)

The system of claim 1, wherein the check for malicious code is conducted in all files and all resources related to the corresponding fully-functional application requiring installation.

### Claim 9 (depends on 1)

The system of claim 1, wherein the check for malicious code is conducted for all files and all resources having an Application ID shared with the functionally-restricted website-related application and the corresponding fully-functional application.

### Claim 10 (depends on 1)

The system of claim 1, wherein the check for malicious code is conducted by analyzing an assetlinks.json file of the website related to the functionally-restricted website-related application launched without installation for a change in relationship between the website and applications initiated by the website.

### Claim 11 (depends on 1)

The system of claim 1, wherein the check tool stops the launch of the functionally-restricted website-related application launched without installation by deleting temporary data needed by the functionally-restricted website-related application.

### Claim 12 (depends on 1)

The system of claim 1, wherein the detection tool, the determination tool, and the check tool are all executed on the mobile device.

### Claim 13 (depends on 1)

The system of claim 1, wherein the detection tool is executed on the mobile device and the determination tool and the check tool are executed on a server operably coupled to the mobile device.

### Claim 14

A method for detecting malicious code for a functionally-restricted website-related application launched without installation on a mobile device, the method comprising:
detecting launch of the functionally-restricted website-related application;
determining at least one parameter of the functionally-restricted website-related application launched without installation;
determining a corresponding fully-functional application requiring installation based on the at least one parameter of the functionally-restricted website-related application launched without installation;
checking for malicious code in the corresponding fully-functional application requiring installation; and
stopping the launch of the functionally-restricted website-related application.

### Claim 15 (depends on 14)

The method of claim 14, wherein stopping the launch of the functionally-restricted website-related application is conducted when the checking for malicious code identifies malicious code.

### Claim 16 (depends on 14)

The method of claim 14, wherein stopping the launch of the functionally-restricted website-related application is conducted prior to checking for malicious code in the corresponding fully-functional application requiring installation, the method further comprising
resuming the functionally-restricted website-related application when malicious code is not identified.

### Claim 17 (depends on 16)

The method of claim 16, wherein stopping the launch of the functionally-restricted website-related application includes simulating user selection of a home key on the mobile device.

### Claim 18 (depends on 14)

The method of claim 14, wherein detecting launch of the functionally-restricted website-related application launched without installation includes detecting an event showing a change in a system display.

### Claim 19

A method of suspending a functionally-restricted website-related application launched without installation on a mobile device, the method comprising:
detecting launch of the functionally-restricted website-related application on the mobile device;
pausing the functionally-restricted website-related application;
determining at least one characteristic of the functionally-restricted website-related application;
resuming the functionally-restricted website-related application based on the determined at least one characteristic.

### Claim 20 (depends on 19)

The method of claim 19, wherein pausing the functionally-restricted website-related application includes deleting temporary data used by the functionally-restricted website-related application or simulating user selection of a home key on the mobile device.
