Rooting Android – Extending the ADB by an Auto-connecting WiFi-Accessible Service

Abstract

Abstract. The majority of malware seen on Android has a top-down approach often targeting application programming interfaces (API) of the financially rewarding telephony and short message service (SMS). In this paper we present a proof of concept of compromising an Android based smartphone by targeting the underlying Linux kernel. We adopt an unorthodox bottom-up approach on modifying the operating system to allow an application to re-route the Android debug bridge (ADB) daemon onto a wireless link. We support our research using case scenarios to show how information can be extracted and inserted into the smartphone without the knowledge of the user. We discuss how the Android build environment can be changed to harness functionality from secured operations. We also discuss how an application can be designed to function with minimum resources, be hidden and perform operations without user consent or interaction. We also provide an overview of how a rooted Android operating system can be misused.

False Sense of Security: A Study on the Effectivity of Jailbreak Detection in Banking Apps

“…To this end, many have focused on Android systems for analyzing apps [40][41][42][43], detecting malware and attacks [44][45][46][47], or finding and describing vulnerabilities [48][49][50]-among many other topics. Moreover, jailbreaking or rooting Android devices is discussed both from an offensive [23,51,52] as well as a defensive point of view [11,33,[53][54][55][56]. In this section, we however focus on the iOS platform for which we first discuss attacks on unmodified as well as jailbroken systems.…”

Network Activity Monitoring Against Malware in Android Operating System

“…It is important to remember that Android's kernel has root permissions disabled by default but the user can gain this kind of permission by running a special crafted piece of code directly to the shell. From the standpoint of Information Security, enabling root permission on an Android device is not recommendable for two important reasons: the user cannot be sure if the rooting software contains any kind of malware such as a backdoor and a rooted device becomes more vulnerable if it gets compromised because any installed malware will get root permissions as well [9].…”

Analyzing User Awareness of Privacy Data Leak in Mobile Applications

“…In addition, the analysis and processing of potentially malicious code occur in a virtualized phone outside of the real mobile device [4,[7][8][9]. Aside from the limited resources, the vulnerabilities [10] of mobile devices and the hacking capabilities from the malware would make the problem more complex than enterprise computing systems.…”