2014
DOI: 10.1109/tifs.2014.2353996
|View full text |Cite
|
Sign up to set email alerts
|

Exploring Permission-Induced Risk in Android Applications for Malicious Application Detection

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
4
1

Citation Types

2
158
0
4

Year Published

2016
2016
2021
2021

Publication Types

Select...
6
1

Relationship

1
6

Authors

Journals

citations
Cited by 317 publications
(164 citation statements)
references
References 22 publications
2
158
0
4
Order By: Relevance
“…In this point it should be noted that none of the related works identify the most relevant features that should be used as input to ML. The only work that select the dominant features is proposed in [16], nevertheless, they focus only on permissions.…”
Section: Resultsmentioning
confidence: 99%
See 2 more Smart Citations
“…In this point it should be noted that none of the related works identify the most relevant features that should be used as input to ML. The only work that select the dominant features is proposed in [16], nevertheless, they focus only on permissions.…”
Section: Resultsmentioning
confidence: 99%
“…For instance how the size of malware subset influence the accuracy. Although some of the related works (i.e., Safedroid [13,16], etc.) report accuracy up to 99%, we believe that our approach, relying on statistical features, can be an alternative option for detecting malware on Android.…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…These algorithms are applied to many fields of machine learning because of being simple and efficient [32,33]. At the same time, the method this paper proposed is compared with the method proposed by Wang [34] and Sato [12]. Wang [34] detected the malware by building different information models from Android permission.…”
Section: Results Contrastmentioning
confidence: 99%
“…At the same time, the method this paper proposed is compared with the method proposed by Wang [34] and Sato [12]. Wang [34] detected the malware by building different information models from Android permission. Sato [12] extracts permission, intent filter (action), intent filter (category) and process name from the AndroidManifest.xml file as the basis of classification, and uses the J48 decision tree to detect the Android malware.…”
Section: Results Contrastmentioning
confidence: 99%