Bad news: Fraudsters have all the tools they need to effectively turn mobile malware into the biggest customer security problem we’ve ever seen. They are lacking just one thing – customer adoption. The number of users who bank online from their mobile devices is still relatively low. Additionally, transactions are not yet enabled for mobile devices on many banks’ websites. Since online fraud is mostly a big numbers game, attacking mobile bankers is not yet an effective fraud operation. But expect a change. In a year from now this is all going to look completely different as more users start banking from their mobile phone and fraudsters release their heavy guns. Trusteer has just released figures predicting that within 12 to 24 months over 1 in 20 (5.6%) of all Android phones and iPads/iPhones could become infected by Mobile malware if fraudsters start integrating zero-day mobile vulnerabilities into leading exploit kits.
Fraudster’s Heaven: Google Android
Android’s security architecture is not currently up to the challenge. This is reflected mainly in the ease of generating powerful fraudulent applications and the ease of distributing these applications. Fraudsters can easily build applications that have access to sensitive operating system resources such as text messages, voice, location, and more. Users installing these applications do get a message with a list of resources the app is requesting access to but would usually ignore it as many applications request access to an extensive list of resources. Building a powerful fraudulent Android application that steals and abuses your identity and your bank account is almost trivial. Distributing these applications on the Android Market is even more trivial. There are no real controls around the submission process that could identify and prevent publishing malicious applications on these stores. Compared to Apple’s App Store, Android Market is the Wild West. You can’t always trust applications you download from it.
Fraudsters have already started to abuse this big security hole. Dozens of malicious applications have already been identified on the Android Market. Google has removed most of them but more keep coming. Trusteer has identified malicious applications on the Android Market which have stayed there for weeks before being taken off by Google. The average user will find it hard to locate this page which allows you to request Google to review and take down inappropriate applications from the Android Market. But don’t expect Google to react fast to anything you submit through this form. We used it a few times with no results. In order to take down an applications in Google Market we actually had to use contacts within Google which are not available to the average user. The process of identifying and removing malicious applications from the Android Market requires major improvements.
Most of the malicious applications which hit Android are not financial. However, in May this year we’ve seen the (already known) Man in the Mobile (MitMo) malware which has previously attacked Symbian, Blackberry, and Windows phones being ported to Android as well. This attack is designed to bypass banks’ SMS Out of Band (OOB) authentication and transaction verification processes. The proximity of this attack to the recent FFIEC guidance which advises banks to consider, among other, Out of Band to fight malware attacks is ironic. It demonstrates exactly why the fraudsters are two steps ahead.
For those of you who don’t know how OOB works here is a short description: The general idea is to fight malware that infects the user’s machine. Once the user browses to a bank’s website from a PC infected with financial malware such as Zeus or SpyEye, the malware takes over the web session and injects fraudulent transactions on behalf of the user. With OOB in place the bank sends a text message to the user’s pre-registered phone number. The message includes the transaction details and a verification code. The user needs to copy the verification code from the mobile device back to the browser on the PC. The assumption is that if the transaction was generated by malware the user will not complete the process and will not copy the confirmation code back to the browser and as a result the bank will not approve the transaction. The MitMo attack breaks this assumption by doing the following: Once the user gets infected and tries to access the bank’s website the malware kicks in and asks the user to download an authentication or security component onto their mobile device in order to complete the login process. The user wrongly assumes this message comes from the bank while in reality it comes from the malware. Once the user installs the malware on the mobile device the fraudsters control both the user’s PC and the user’s phone. Next the malware generates a fraudulent transaction on behalf of the user. The bank then sends a confirmation message to the user’s mobile device. The malware on the user’s device reads the confirmation message and sends it to the malware on the PC. It then deletes the confirmation message from the user’s mobile device so the user will not see it. The malware on the user’s PC enters the confirmation code and approves the transaction.
MitMo Attack Cycle
The Android malware that spread On May this year came in different flavors. One of the flavors was even using the Trusteer brand to gain users trust and convince them to download the application. The malware itself was used in conjunction with Zeus 22.214.171.124. The user was first infected with Zeus on their PC and then Zeus showed the message requesting the user to download the Android malware component.
MitMo fraudulent Android Application Abusing the Trusteer brand
People who had already downloaded Trusteer Rapport are protected from this type of attack.
Apple iOS is not as Secure as One May Think
iOS is the operating system of the iPhone, iPad, and iPod. With iOS malware, it’s a slightly different story. It’s not easy to create malicious applications that have access to device resources since iOS applies strict access control on applications. It’s also not easy to introduce malicious applications on the App Store as Apple conducts a manual review of each submitted application which allows them to detect abusing applications. However, there is a hole in this security architecture and it’s called jailbreaking. A jailbroken iOS device doesn’t enforce access control and basically allows any app to do whatever it wants on the device. Unfortunately many users jailbreak their devices as they want to run all sorts of applications that are not on the App Store. But what’s more unfortunate is that vulnerabilities in iOS could allow malicious websites to jailbreak a device and infect it with malware without the user’s consent or knowledge. Last week we saw a good example for that.
JailbreakMe.com published an exploit which allows the automated jailbreaking of iOS devices from a specially created Web site. PDF files that exploit this vulnerability are reportedly publicly available. Even clicking a crafted PDF document or surfing to a website with the PDF documents are sufficient to infect the mobile device with malware. Now the concept of malicious websites serving exploits to infect endpoint devices is well mastered by fraudsters. The notorious BlackHole exploit kit and other exploit kits such as Fragus and Neosploit provide automation of these processes. BlackHole is extremely dangerous and widely used as it is distributed for free. Millions of websites are being compromised to run these exploit kits.
When users browse to one of these compromised websites they get infected with malware. Note that fraudsters can use the same exploit kit to serve any piece of malware they choose. Once the authors of BlackHole add iOS vulnerabilities to their kit we’ll start seeing a quick increase in malware distribution on iOS devices. This recent vulnerability is not the first which allows fraudsters to compromise iOS devices and it won’t be the last. We’re looking at just the beginning of this problem. Fraudsters will continue to research iOS and discover more vulnerabilities which will allow them to compromise devices and commit fraud. I hope I’m wrong, but a year from now this can become so common that it will not even hit the news.
In the US alone 50% of mobile phones are smart phones with Android and iPhone being the clear market leaders. In April of this year Toronto-based Solutions Research Group survey among smartphone users showed that and 38% of them use a banking application. These two numbers are on constant increase and are just about to become big enough for fraudsters to start using their heavy guns. All the building blocks are in place: Fraudsters are researching iOS and Android for vulnerabilities, they have effective exploit kits which can automate this process, they have large scale operations which compromise websites and force them to distribute malware, and they have effective malware for mobile which can commit fraud. In my opinion, this all leads to one conclusion – we are about to face one of the worse security problems ever and it won’t be long before we do.
Anti-malware solutions for mobile phones are hardly the answer to this problem. These solutions are not much different than their PC counterparts. They’re based on scanning applications installed on the device against a list of known malicious applications. This type of solution cannot scale when the number of malicious applications explodes. As mobile malware numbers increase we’re about to face the very same problem we’re currently facing with desktop anti-virus solutions- low effectiveness.
A different solution that takes a different approach for mobile security is required – one that can protect these devices from getting infected to begin with and can protect mobile communication with banks from malware that may end up on the device. This concept which has been successfully used by Trusteer Rapport to protect 150 banks across the world is now available for the iOS and Android. Trusteer Mobile will be launched later this year together with a handful leading banks and is going to change the way banks and their customers think of mobile security.
Recommendations to secure mobile banking:
- Check rating, user reviews, and comments for each mobile application you download. Avoid low rated, new applications, and bad reviews.
- Carefully review the permission requested by Android applications when you install them. Applications that ask for access to text messages and other sensitive information should raise a red flag and further researched before you download it
- Have your PC protected with an online banking security software such as Trusteer Rapport, which you can download from your bank’s website. This software can break MitMo attacks by not allowing fraudsters control the web channel.
- Regularly install updates for your mobile device
Calculation of smart phone infection rates for zero day exploits
Trusteer statistics for June 2011 show that each day one out of 1500 users accesses a website which was infected with the BlackHole exploit kit. Out of a million users 667 users will access the BlackHole exploit kit every day. Assuming the BlackHole exploit kit incorporates a Zero Day vulnerability like the recent JailBreakMe vulnerability indicates 667 infected users a day per 1 million users. Assuming it takes Apple or Google one week to fix the vulnerability and then it takes in average 2 weeks for users to update their mobile phone with a new release, indicates 21 days of exposure on average in which 14,000 user per million users will get infected with the Zero day attack. Assuming 4 of these zero day exploits a year we’re looking at 56,000 infection a year per million users which is 5.6% – an extremely high number.
Posted in English-Italian Translations, Trusteer and tagged Android, IOS, OOB by admin with no comments yet.
The Symbian, Windows Mobile and Blackberry modules of the notorious Zeus malware toolkit (also known as ZBot) have been known about for some months, and it has been clear that Zeus gang was interested in developing malware for mobile platforms.
However, until now we have not seen any evidence of Zeus targeting users who own Android or iOS (iPhone/iPad) devices.
This fact was quite surprising to us, considering the popularity of the Android and iOS platforms and the growing prevalence of malware being written for the Google Android operating system in particular.
In the last couple of days, however, there has been quite a lot of discussion on the mobile malware analysis mailing lists about a version of a an Android version of Zeus.
We eventually concluded that this was a malicious application that Sophos products have been detecting as Andr/SMSRep-B since 31st May 2011.
The malicious application pretends to be an Android version of Trusteer Rapport banking security tool, and was served to devices running the Google Android OS by a web server which was set up to deliver Zbot malware to multiple platforms.
After the fact, it was not difficult to connect the Android application with Zeus toolkit, although we could not conclude 100% that there was a connection.
The installed application uses a stolen Rapport icon and displays a simple screen when launched on affected device.
The fake Rapport application registers a Broadcast receiver which intercepts all received SMS messages and forwards the messages to a malicious web server using HTTP POST requests. The stolen SMS messages are encoded using a JSON encoding scheme, often used by various web services.
Although the application is clearly designed to steal the content of SMS messages, its not very sophisticated.
That’s why we cannot be 100% sure that this is indeed a part of the Zeus kit. The URL of the command and control server is hard-coded into the source code, for example, which makes the application quite inflexible for installation on an alternative server.
Nevertheless, this malicious Android application is interesting as it combines spyware functionality with the concept of fake security software. As we’ve seen recently in the Mac OS X world, fake anti-virus software is one of the most common themes adopted by malicious hackers in their attacks.
Eventually, the doubt whether this is really part of the Zeus family or not remains.
I suppose only the developers of Zeus kit know for certain. Unfortunately I have no means of contacting them, and even if I did I doubt they would be prepared to confirm or deny this theory.
Posted in Naked Security, English-Italian Translations and tagged Android, IOS, Trusteer Rapport, ZBot, ZeuS by admin with no comments yet.