Who is rooting your Android?

happygeek 0 Tallied Votes 498 Views Share

With the recent announcement of an easy way to gain root access for Android phones running 2.3.4, to add to the list of similar exploits for earlier versions and 3.0 and beyond, it should come as no real surprise that the bad guys are taking advantage of the relative weakness of the Android OS when compared to iOS devices.

According to the latest FortiGuard Labs report looking at the top five Android Malware Families, there are approximately five times the number of malicious families on the Android OS as compared Apple's iOS. Of course, some of this will be down to market share considerations as Android devices now accounts for 52.2% of global smartphone OS market share whereas iOS on 18% is in third place behind Symbian.

But it does not account for the sheer scale of the Android malware explosion which, according to Axelle Apvrille who is a senior mobile anti-virus researcher at Fortinet, can be attributed to "the way Apple handles iOS application development and distribution. Unlike Android, which makes it fairly easy to place applications for people to download, iOS requires developers to undergo some strict screening from Apple before the application can make it to the Apple Store. That's not to say that Apple is totally immune from being infiltrated by malware - the Eeki banking worm proves that - but it is a testament to why we're seeing so little activity on the iOS platform".

Comparing 2011 to 2010, the FortiGuard Labs researchers noticed a 90% increase in Android malware families year on year. iOS malware families only increased by 25%, although neither figure takes account of actual infection rates or the dangerousness of any particular malware family, so perhaps should be taken with a large pinch of salt.

Those Android rooting vulnerabilities, on the other hand, should be considered totally salt free. Only last month Jon Larimer and Jon Oberheide for Android platform 2.3.6 that revealed an easy way for hackers and malicious software developers to gain and exploit root access to an Android device. The bad guys are, obviously, taking notice and once they have a method to gain root access to your mobile device the silent downloading of malicious software becomes child's play.

Anyway, the top five malware families for which FortiGuard Labs received the most samples in 2011 were:
Geinimi
Android's first botnet, which sends a victim's geographic location and controls his/her phone remotely. For example, Geinimi can force the infected phone call a given phone number.
Hongtoutou
A Trojan live wallpaper that steals private information such as the victim's subscriber number (IMSI) and automatically visits Websites that the malware directs it to.
DroidKungFu
Another botnet that has multiple capabilities such as remotely installing other malware, remotely starting specific applications and adding bookmarks.
JiFake
A fake instant messenger application that sends SMS messages to premium phone numbers
BaseBridge
A Trojan that sends SMS messages to premium numbers

Dani AI

Generated

The original post is right to flag rooting as the single biggest escalation risk, but the threat needs three clarifying points so the thread’s advice is practical.

First, commodity Android malware in 2011 didn’t rely on one delivery method. Campaigns such as DroidDream and DroidKungFu packaged exploits to escalate privileges and install additional payloads without user consent. These cases show how an app can carry its own privilege-escalation code and then expand its capabilities once it succeeds. (malware.unam.mx)

Second, is also correct that ADB/USB debugging is a privileged channel and a useful vector when it’s enabled — it’s a developer feature that you must explicitly turn on. But attackers have used other paths too: repackaged apps, malvertising and update-style attacks that exploit OS or app bugs to install or run extra code. In short, turning off developer options reduces one big risk, but it does not eliminate exploit-driven escalation. (developer.android.com)

Practical checklist (actions that still protect years later):

  • Keep Developer options and USB debugging OFF when not actively developing. (developer.android.com)
  • Block installs from unknown sources (or the Install unknown apps setting on newer Android); only install apps from trusted stores and vet publishers/permissions. (developer.android.com)
  • Revoke ADB authorizations, remove unknown Device Admin apps, and inspect installed packages for odd names. Use an MDM/Device Policy in managed fleets to enforce these settings where possible. (developer.android.com)

Quick checks/remediation (from a computer with ADB available):

adb devices
adb shell ls -l /system/bin/su /system/xbin/su
adb shell pm list packages | grep suspicious

If a device was rooted by malware, a factory reset only wipes userdata/cache on most devices; it may not remove changes to system/vendor/boot partitions — in those cases re-flashing the official factory image (or getting vendor support) is the reliable way to restore a clean system. (android.googlesource.com)

These steps bridge the two positions already posted: lock down developer channels (as recommends) and treat exploit-driven rooting as a live risk vector (as warned).

Trigle 0 Newbie Poster

So basically, you're saying that, an exploit which in the pictures shows it being executed via adb shell access, which is a developer tool and only available using USB debugging mode which should be off by default. In order to allow the features which the debug bridge gives, elevation must occur and therefore some loopholes have come into effect.

This article simply seems like iOS fanboiism to me..

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.