Welcome Guest. | Log In | Register | Membership Benefits

GingerMaster Is First Malware To Utilize A Root Exploit On Android 2.3

New attack can successfully avoid detection by antivirus programs, university research team says

Aug 21, 2011 | 12:17 AM | 

By Tim Wilson
Dark Reading
Researchers at North Carolina State this week disclosed details on new malware that they say is the first to exercise a root-level exploit against Android 2.3.

The university research team, in collaboration with NetQin, identified new high-risk malware GingerMaster, which they say is the first Android malware that utilizes a root exploit against Android 2.3 (also known as Gingerbread). GingerMaster takes advantage of the most recent root exploit against Android platform 2.3, which was discovered in April, the team says in a blog.

"As this is the first time such malware has been identified, it is not surprising when our experiments show that it can successfully evade the detection of all tested leading mobile antivirus software," the blog states.

The GingerMaster malware is repackaged into legitimate apps, the researchers say. "Within the repackaged apps, it will register a receiver so that it will be notified when the system finishes booting," the blog says. "Inside the receiver, it will silently launch a service in the background [that can] collect various information, including the device id, phone number, and other [data] and then upload them to a remote server."

After getting root privilege, GingerMaster malware will connect to the remote command-and-control server and wait for instructions, the research team says. "According to our investigation, the GingerMaster malware has the payload to silently download and install the app without users' awareness," the blog states.

"Due to the fact that GingerMaster contains the most recent root exploit, we consider it poses one of the most serious threats to mobile users," the North Carolina State team says. The team recommends "common sense" defenses, such as sticking to known app markets and taking care when giving out access permissions.

Have a comment on this story? Please click "Comment" below. If you'd like to contact Dark Reading's editors directly, send us a message.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Authentication Reports

report What's Next for Certificate Technology
A recent rash of certificate authority breaches has left a bad taste in many people's mouths. There is no one reason for the breaches. The compromises were the result of a breakdown in people, processes and technology, but not necessarily the certificates themselves. We take a look at what?s wrong with certificate technology, what can be done to fix it, and what's down the road for certificates and CAs.

report Will Smartcards Live Up to Their Name?
Recent compromises of smartcard data have exacerbated concerns about the technology?s privacy, security and standards (or lack thereof). Yet the promise of smartcards is too compelling to ignore. New technologies and applications prompt us to take a fresh look.

report Get The Best Of Biometrics
As data volume and sensitivity grow, companies cannot rely on password- and token-based authentication. Biometrics can be used to provide strong access control, but you must weigh added complexity and costs against assurance that users are who they say they are.

Other reports from the Authentication Tech Center:




Featured Webcasts
Featured Whitepapers
Featured Reports