Last weekend saw the (somewhat anticipated) discovery of an interesting mobile trojan – the first spotting of a file-encrypting ransomware for Android by our detection engineers.
Let’s put this all into perspective, so we know what we’re dealing with here…
Almost exactly one year ago, a hybrid comprising characteristics of a rogue AV and ransomware (the lockscreen type, not a file-encryptor) was discovered, calling itself Android Defender, as reported by Symantec. It had all the typical traits of a fake AV and all the typical traits of a lockscreen ransomware – in that it was not actually that trivial to get rid of when a user was not protected by a mobile antivirus, they had to disable it by booting their device into Safe mode. ESET detects it as Android/FakeAV. And a less aggressive Android Defender without the lockscreen functionality was analyzed by Sophos in May 2013.
Last month the blog Malware don’t need Coffee reported on a police ransomware for Android by the Reveton team. Again, this was an evolutionary migration of a malware type very prevalent in the recent years from Windows to the Android platform. Although some connection to Cryptolocker (one of many file-encrypting trojans, which ESET detects as the Win32/Filecoder family, that received an overwhelming amount of media attention and that I have written about here and here) was suggested by Kaspersky, the malware, detected by ESET as Android/Koler was neither Cryptolocker, nor did it encrypt any files on the infected device.
That, however, changed with the most recent discovery, last weekend. This Android trojan, detected by ESET as Android/Simplocker , after setting foot on an Android device, scans the SD card for certain file types, encrypts them, and demands a ransom in order to decrypt the files. Let’s look at the malware in greater detail.
After launch, the trojan will display the following ransom message and encrypt files in a separate thread in the background.
Figure 1 – Android/Simplocker.A ransom message
The ransom message is written in Russian and the payment demanded in Ukrainian hryvnias, so it’s fair to assume that the threat is targeted against this region. This is not surprising, the very first Android SMS trojans (including Android/Fakeplayer) back in 2010 also originated from Russia and Ukraine. The message roughly translates to:
WARNING your phone is locked!
The device is locked for viewing and distribution child pornography , zoophilia and other perversions.
To unlock you need to pay 260 UAH.
1. Locate the nearest payment kiosk.
2. Select MoneXy
3. Enter {REDACTED}.
4. Make deposit of 260 Hryvnia, and then press pay.
Do not forget to take a receipt!
After payment your device will be unlocked within 24 hours.
In case of no PAYMENT YOU WILL LOSE ALL DATA ON your device!”
The malware directs the victim to pay using the MoneXy service for obvious reasons, as it is not as easily traceable as using a regular credit card. 260 UAH is roughly 16 EUR.
Android/Simplocker.A will scan the SD card for files with any of the following image, document or video extensions: jpeg, jpg, png, bmp, gif, pdf, doc, docx, txt, avi, mkv, 3gp, mp4 and encrypt them using AES.
Files encrypted by Android/Simplock.A
It will also contact its Command & Control server and send identifiable information from the device (like IMEI, et cetera). Interestingly, the C&C server is hosted on a TOR .onion domain for purposes of protection and anonymity.
Figure 3 – Part of the Android/Simplocker.A source code for connecting to the TOR anonymity network
As you may notice on the nag-screen above, there is no input field for a payment-confirming code of any kind, as we’ve seen in earlier examples of Windows ransomware. Instead, the malware listens to its C&C server for a command – probably issued after payment is received – to decrypt the files.
The sample we’ve analyzed is in the form of an application called ‘Sex xionix’. It was not found on the official Google Play and we estimate that its prevalence is very low at this time.
Our analysis of the Android/Simplock.A sample revealed that we are most likely dealing with a proof-of-concept or a work in progress – for example, the implementation of the encryption doesn’t come close to “the infamous Cryptolocker” on Windows.
Nevertheless, the malware is fully capable of encrypting the user’s files, which may be lost if the encryption key is not retrieved. While the malware does contain functionality to decrypt the files, we strongly recommend against paying up – not only because that will only motivate other malware authors to continue these kinds of filthy operations, but also because there is no guarantee that the crook will keep their part of the deal and actually decrypt them.
Instead we encourage users to protect themselves against these threats by prevention (by using our ESET Mobile Security for Android, for example and adhering to best security practices, such as keeping away from untrustworthy apps and app sources) and if they are unfortunate to already be infected to recover the files from a backup. Because when you have a backup, then any Filecoder trojan – be it on Android, Windows, or any operating system – is nothing more than a nuisance.
Analysed Sample SHA1: 808df267f38e095492ebd8aeb4b56671061b2f72
Kudos to Marek Luptak for his analysis of this Android trojan.
The post ESET Analyzes First Android File-Encrypting, TOR-enabled Ransomware appeared first on We Live Security.
Brought by: http://foodonia.com
ليست هناك تعليقات:
إرسال تعليق
اترك تعليقا .. http://foodonia.com