MaMaDroid: detecting Android malware by building Markov chains of behavioral models (extended version)

FOS: Computer and information sciences Cryptography and security Artificial intelligence Computer Science - Cryptography and Security 000 Computer Science - Artificial Intelligence 02 engineering and technology Computer Science Research Centre 004 Artificial Intelligence (cs.AI) Android, malware detection, static analysis 0202 electrical engineering, electronic engineering, information engineering Cryptography and Security (cs.CR)
DOI: 10.48550/arxiv.1711.07477 Publication Date: 2019-04-09
ABSTRACT
As Android has become increasingly popular, so has malware targeting it, thus motivating the research community to propose different detection techniques. However, the constant evolution of the Android ecosystem, and of malware itself, makes it hard to design robust tools that can operate for long periods of time without the need for modifications or costly re-training. Aiming to address this issue, we set to detect malware from a behavioral point of view, modeled as the sequence of abstracted API calls. We introduce M A M A D ROID , a static-analysis-based system that abstracts app’s API calls to their class, package, or family, and builds a model from their sequences obtained from the call graph of an app as Markov chains. This ensures that the model is more resilient to API changes and the features set is of manageable size. We evaluate M A M A D ROID using a dataset of 8.5K benign and 35.5K malicious apps collected over a period of 6 years, showing that it effectively detects malware (with up to 0.99 F-measure) and keeps its detection capabilities for long periods of time (up to 0.87 F-measure 2 years after training). We also show that M A M A D ROID remarkably overperforms D ROID APIM INER , a state-of-the-art detection system that relies on the frequency of ( raw ) API calls. Aiming to assess whether M A M A D ROID ’s effectiveness mainly stems from the API abstraction or from the sequencing modeling, we also evaluate a variant of it that uses frequency (instead of sequences), of abstracted API calls. We find that it is not as accurate, failing to capture maliciousness when trained on malware samples that include API calls that are equally or more frequently used by benign apps.
SUPPLEMENTAL MATERIAL
Coming soon ....
REFERENCES ()
CITATIONS ()
EXTERNAL LINKS
PlumX Metrics
RECOMMENDATIONS
FAIR ASSESSMENT
Coming soon ....
JUPYTER LAB
Coming soon ....