On the Need of Precise Inter-App ICC Classification for Detecting Android Malware Collusions
Karim O. Elish, Danfeng (Daphne) Yao, and Barbara G. Ryder Department of Computer Science Virginia Tech
May 21, 2015
Malware Collusions Karim O. Elish, Danfeng (Daphne) Yao, and - - PowerPoint PPT Presentation
On the Need of Precise Inter-App ICC Classification for Detecting Android Malware Collusions Karim O. Elish, Danfeng (Daphne) Yao, and Barbara G. Ryder Department of Computer Science Virginia Tech May 21, 2015 Problem and Motivation Malware
May 21, 2015
2
– Directly: Android Intent-based inter-component communication (ICC) – Indirectly: shared files,…etc.
3
An example of permissions and operations being split between colluding apps
Solution Analysis Type Collusion Classification Policies Limitation XManDroid [NDSS’12]
Permissions Combinations
CHEX [CCS’12]
No
ComDroid [MobiSys’11]
No
to critical operation -> false alerts Epicc [USENIX13]
No
Amandroid [CCS’14]
No
among apps
4
5
6
– <ICCNamek, sourceComponentk, targetComponentk, typeOfCommunicationk>, Partial ICC map for “abc.ssd.TrafficInfoCheck” app
7
Existing collusion detection solution (XManDroid) triggers a large number of false alerts in benign app pairs (11 out of 20 benign app pairs are misclassified as collusion) 8
1 2 3 4 5 6 7 8 9 Policy # 8 Policy # 9 Policy # 10 Policy # 11 # of App Pairs
Subset of XManDroid’s policy
channels with fine granularity
with low false alerts
9
10
11
12
13