Document Title:
===============
HITB2011KUL - Reverse Engineering Android Malware


References:
===========
Download:	http://www.vulnerability-lab.com/resources/videos/413.wmv
View: 		http://www.youtube.com/watch?v=22KVTR4mEIk



Release Date:
=============
2012-02-02


Vulnerability Laboratory ID (VL-ID):
====================================
413


Discovery Status:
=================
Published


Exploitation Technique:
=======================
Event


Severity Level:
===============
High


Technical Details & Description:
================================
Android is growing at such an explosive rate, and users are storing an increasing amount of 
important data on their mobile phones, thus the platform is an attractive target for malware 
author. Malware author are aiming for users of Google’s Android mobile operating system with 
a malicious application that harvests personal information, controlling the system and sends 
it to a remote server. By utilizing SMS toll fraud; malware author will also steal money from 
infected mobile phone.

Malware infection on Android platform is going to be interesting in future (it’s happening now!). 
Thus, reversing Android Malware (Droid-ware) is interesting challenge to address. Malware analysis 
can be performed using two approaches, which is Dynamic Analysis and Dead-Listing Analysis 
(Reverse Engineering). Reverse engineering is a vitally important skill for today’s expert security 
professional. In this presentation, we’ll focus on the later approach to analyze Android Malware.

In this talk, the speaker will discuss on recent progress on Android malware scene. The speaker 
will provide details on few recent Android Malware samples. The speaker will also discuss on 
technical analysis on malicious Android applications by using reversing engineering approach. 
The analysis parts will focus on dissecting obfuscation such as encryption, string optimizing and 
generic obfuscation techniques applied inside Android Malware. The challenges when dealing with 
reversing Android Malware will be addressed as well.


Credits & Authors:
==================
Mahmud Ab Rahman currently works as Information Security Specialist for Malaysia Computer Emergency 
and Response Team (MyCERT) under umbrella of CyberSecurity Malaysia. Prior to that, he worked as an 
Intrusion Analyst at MyCERT department. His education background comprises of Master Degree in 
Computer Science from National University of Malaysia in 2006. Prior to that, he obtained a Degree 
in Computer Science from the same university.

Mahmud has been involved in the computer security field for over 5 years. His area of focus and 
interest is network security, honeynet, botnet monitoring, and malware analysis. He also engages 
in several large scale penetration-testing exercises and to provide solutions for any vulnerability 
detected. Moreover, he is recognized for conducting numbers of training for organizations to talk 
on topics ranging from introduction to advanced security courses. He is a occasional speaker at 
conferences such as FIRST AGM, FIRST TC,Honeynet Annual Workshop and Infosec.MY. He currently 
certified for SANS’s GPEN (gold) and GREM.


Disclaimer & Information:
=========================
The information provided in this advisory is provided as it is without any warranty. Vulnerability-Lab disclaims all warranties, 
either expressed or implied, including the warranties of merchantability and capability for a particular purpose. Vulnerability-
Lab or its suppliers are not liable in any case of damage, including direct, indirect, incidental, consequential loss of business 
profits or special damages, even if Vulnerability-Lab or its suppliers have been advised of the possibility of such damages. Some 
states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation 
may not apply. We do not approve or encourage anybody to break any vendor licenses, policies, deface websites, hack into databases 
or trade with fraud/stolen material.

Domains:    www.vulnerability-lab.com   	- www.vuln-lab.com			       - www.vulnerability-lab.com/register
Contact:    admin@vulnerability-lab.com 	- support@vulnerability-lab.com 	       - research@vulnerability-lab.com
Section:    video.vulnerability-lab.com 	- forum.vulnerability-lab.com 		       - news.vulnerability-lab.com
Social:	    twitter.com/#!/vuln_lab 		- facebook.com/VulnerabilityLab 	       - youtube.com/user/vulnerability0lab
Feeds:	    vulnerability-lab.com/rss/rss.php	- vulnerability-lab.com/rss/rss_upcoming.php   - vulnerability-lab.com/rss/rss_news.php

Any modified copy or reproduction, including partially usages, of this file requires authorization from Vulnerability Laboratory. 
Permission to electronically redistribute this alert in its unmodified form is granted. All other rights, including the use of other 
media, are reserved by Vulnerability-Lab Research Team or its suppliers. All pictures, texts, advisories, sourcecode, videos and 
other information on this website is trademark of vulnerability-lab team & the specific authors or managers. To record, list (feed), 
modify, use or edit our material contact (admin@vulnerability-lab.com or support@vulnerability-lab.com) to get a permission.

    				   	Copyright © 2012 | Vulnerability Laboratory