Malware detection techniques and tools for Android Online publication date: Sun, 25-Jun-2017
by Sangeeta Rani; Kanwalvir Singh Dhindsa
International Journal of Social Computing and Cyber-Physical Systems (IJSCCPS), Vol. 1, No. 4, 2016
Abstract: Smartphone, with its powerful capabilities, has been wildly used in every area of our day-to-day life. The enormous kinds of applications installed in these smartphones like WhatsApp and Viber have changed the way people live and communicate. An estimate by Gartner indicates that 90% of the phones by the end of 2018 will be smartphones (MobileStorm, 2014). The most popular mobile operating system today in the industry is Android. However, with the prevalence of Android smartphone, malware authors have started to target it. Although mobile anti-malware solutions could be installed to scan malicious apps before they are made available for download, existing mobile anti-malware software relies exclusively upon a prior knowledge of malware samples in order to extract and deploy signatures for subsequent detection. Moreover, malware writers may update existing malware samples to dodge detection. Hence, this imprudent nature makes them inadequate in identifying new or mutated malware. This paper explores different techniques and tools available to analyse and detect Android malware. It also highlights the features and limitations of these techniques and tools.
Online publication date: Sun, 25-Jun-2017
If you are not a subscriber and you just want to read the full contents of this article, buy online access here.Complimentary Subscribers, Editors or Members of the Editorial Board of the International Journal of Social Computing and Cyber-Physical Systems (IJSCCPS):
Login with your Inderscience username and password:
Want to subscribe?
A subscription gives you complete access to all articles in the current issue, as well as to all articles in the previous three years (where applicable). See our Orders page to subscribe.
If you still need assistance, please email firstname.lastname@example.org