# US 2019/0174319 A1 · Detection and identification of potentially harmful applications based on detection and analysis of malware/spyware indicators

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

- Number: US 2019/0174319 A1
- Document ID: US20190174319A1
- Status: Published application
- Kind: A1
- Application number: 16/206,020
- Filed: 2018-11-30
- Published: 2019-06-06
- Earliest claimed: 2017-12-01
- Assignees: Seven Networks, LLC
- Applicants: Seven Networks, LLC
- Inventors: Ari Backholm; Ross Bott; Dustin Morgan; Colby Adams
- Web page: https://patentgrep.com/patent/US20190174319A1

## CPC

- H04W 12/128: Anti-malware arrangements, e.g. protection against SMS fraud or mobile malware
- H04L 63/0281: {Proxies}
- H04L 63/1425: {Traffic logging, e.g. anomaly detection}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- H04W 12/30: Security of mobile devices; Security of mobile applications
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for detecting and identifying malware/potentially harmful applications based on behavior characteristics of a mobile application are disclosed. One embodiment of a method of detecting a potentially harmful application includes detecting behavior characteristics of a mobile device and, based on those detected behavior characteristics, identifying one or more indicators that the mobile application is a potentially harmful application. Those indicators are then analyzed to determine whether the application is a potentially harmful application.

## Claims

### Claim 1

A malware detector, comprising:
a data traffic monitor that detects data traffic of a mobile application on a mobile device;
an activity monitor that detects characteristics of behavior of the mobile application; and
an analysis engine that identifies, based on the data traffic of the mobile application and the characteristics of behavior of the mobile application, one or more indicators that the mobile application is a potentially harmful application and determines, based on an analysis of the one or more indicators, whether the mobile application is a potentially harmful application.

### Claim 2 (depends on 1)

The malware detector of claim 1, wherein the analysis engine identifies one or more indicators that the mobile application is a potentially harmful application based on upload activity of the mobile application.

### Claim 3 (depends on 2)

The malware detector of claim 2, wherein the upload activity used to identify one or more indicators includes data traffic containing personal information about a user of the mobile application or the mobile device.

### Claim 4 (depends on 1)

The malware detector of claim 1, wherein the analysis engine identifies one or more indicators that the mobile application is a potentially harmful application based on behavior of the mobile application while the mobile application is operating in the background.

### Claim 5 (depends on 4)

The malware detector of claim 4, wherein the behavior of the mobile application while the mobile application is operating in the background includes tracking the user's behavior on the mobile device.

### Claim 6 (depends on 1)

The malware detector of claim 1, wherein the analysis engine uses machine learning to identify one or more indicators that the mobile application is a potentially harmful application and to determine whether the mobile application is a potentially harmful application.

### Claim 7 (depends on 1)

The malware detector of claim 1, wherein the malware detector is communicatively coupled to a remote server that provides information to the malware detector that the analysis engine uses for identifying that the mobile application is a potentially harmful application.

### Claim 8

A mobile device, comprising:
a memory; and
a processor,
wherein the processor is configured to:
monitor data traffic associated with a mobile application of the mobile device;
monitor device behavior of the mobile device; and
detect malware based on the data traffic and the device behavior,
wherein the processor detects malware by identifying one or more indicators and analyzing the one or more indicators.

### Claim 9 (depends on 8)

The mobile device of claim 8, wherein the one or more indicators used to detect malware are identified based on upload activity of the mobile application.

### Claim 10 (depends on 9)

The mobile device of claim 9, wherein the upload activity that is used to identify one or more indicators includes data traffic containing personal information about a user of the mobile application or the mobile device.

### Claim 11 (depends on 8)

The mobile device of claim 8, wherein monitoring the device behavior includes monitoring activities of the mobile application while the mobile application is operating in the background.

### Claim 12 (depends on 11)

The mobile device of claim 11, wherein the processor identifies one or more indicators when the mobile application is operating in the background based on the mobile application tracking the user's behavior on the mobile device while the mobile application is operating in the background.

### Claim 13 (depends on 8)

The mobile device of claim 8, wherein analyzing the one or more indicators includes comparing the one or more indicators with information determined using machine learning.

### Claim 14 (depends on 8)

The mobile device of claim 8, wherein the processor is further configured to flag detected malware.

### Claim 15

A method of detecting a potentially harmful application, comprising:
monitoring data traffic of a mobile application on a mobile device;
detecting characteristics of behavior of the mobile application;
identifying one or more indicators that the mobile application is a potentially harmful application,
wherein the one or more indicators are based on the data traffic of the mobile application and the characteristics of behavior of the mobile application;
analyzing the one or more indicators to determine whether the mobile application is a potentially harmful application; and
classifying the mobile application as a potentially harmful application based on the analysis of the one or more indicators.

### Claim 16 (depends on 15)

The method of claim 15, wherein the one or more indicators are based on upload activity of the mobile application.

### Claim 17 (depends on 15)

The method of claim 15, wherein the one or more indicators are based on behavior of the mobile application while the mobile application is operating in the background.

### Claim 18 (depends on 15)

The method of claim 15, wherein a threshold associated with a first indicator is determined using machine learning.

### Claim 19 (depends on 15)

The method of claim 15, wherein a threshold associated with a first indicator is determined based on information provided by a third party.

### Claim 20 (depends on 15)

The method of claim 15, wherein classifying the mobile application as a potentially harmful application is based on the presence of a plurality of indicators.
