Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

03:00 PM
Connect Directly

'Asacub' Trojan Converted To Mobile Banking Weapon

In a sign of the times, what was once a routine data-stealing tool has evolved into a dangerous mobile banking threat.

In another sign that threat actors have begun turning their sights on mobile devices, Kaspersky Labs has uncovered a new banking Trojan targeting Android users in the US, Russia, and Ukraine.

The malware, dubbed Asacub, has apparently been around since last June and was originally used mainly for stealing browser histories, contact lists, and other data from infected devices. In its original form, Asacub was also designed to steal and forward incoming SMS messages to a remote malicious server, turn off the phone screen, and send SMS messages to targeted users on behalf of the device owner.

However, researchers at Kaspersky Lab last fall began coming across new versions of Asacub with features similar to those found in banking Trojans. For example, malicious files in the new versions of the Trojan contained phishing screens with the logos of major European banks.

“Phishing screens were present in all the modifications of Asacub created since September that are known to us, but only the window with bank card entry fields was used," said Kaspersky mobile threats expert Roman Unuchek in a blog post describing the new threat. That means the operators of Asacub plan on targeting only the users of banks whose logos they use, or that a version of the Trojan exists that already does so, he said.

The original data-stealing Asacub has been modified in other ways as well to function more as a banking Trojan. For instance, the malware now supports a much wider range of functions than the original. In addition to uploading browser, contact, and installed application data to a remote server, the modified Asacub can also display a bank phishing window, enable call forwarding, send and intercept SMS messages, and run specified Unstructured Supplementary Service Data (USSD) requests. USSD requests basically allow communication with cellular operators or mobile services without making calls and sending SMS.

This latest version of Asacub supports additional capabilities like tracking and sending current location data, and taking a snapshot using the device camera.

So far, there is nothing to suggest that Asacub has been used to target US consumers. But the logo of a major US bank was spotted on some versions of the malware, suggesting that an attack could be activated at any time, Unuchek said.

Asacub is another signal of what many predict will be an increase in malware attacks against mobile devices in the near future. It is the second banking Trojan targeting Android users that security vendors have warned about in just the past few days.

Last week, Symantec issued an alert on Bankosy, a data-stealing Trojan that, like Asacub, has been modified to target users of certain banks. According to Symantec, the malware is capable of intercepting SMS messages as well as the voice calls that banks sometimes send to customers as a second form of authentication when a consumer tries to log into an account or carry out certain transactions.

In December, FireEye warned of SlemBunk, a family of Android Trojans rigged to look like the legitimate apps of nearly three dozen financial institutions and service providers scattered across North America, the Asia Pacific, and Europe. FireEye described the malware as capable of harvesting the login credentials of users of certain banks and banking-related apps.

And for the first time ever, two Android mobile banking Trojans -- Faketoken and Marcher -- ended up on Kaspersky Labs’ list of the Top 10 banking Trojans of 2015.

Some security analysts believe that application misuse and lost devices still pose the greatest short-term threat to mobile security -- not malware. But the trend has some analysts advocating that enterprises begin taking precautions against mobile malware.

In a Gartner blog post last September, Gartner analyst Dionisio Zumerle noted that the industry has witnessed an increase in “the development of mobile attacks that can be applied across the enterprise, are more realistic, can be exploited remotely and can do greater damage.”

“However, we have yet to see these attacks translate into actual damages for organizations,” he said.

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Recommended Reading:

Comment  | 
Print  | 
More Insights
Threaded  |  Newest First  |  Oldest First
User Rank: Apprentice
1/22/2016 | 3:37:42 AM
best user practice?
What is the best user practice to avoid these Trojans ?

Article is very informative 
User Rank: Ninja
1/24/2016 | 4:47:59 PM
Static Frameworks for Long-term Trojans
I'll be cautious in the wording here, but more and more Trojans are being written using pluggable and extensible frameworks.  Perhaps it used to be that writing small Trojans regularly with different code signatures helped keep these guys from getting discovered by both people and software. But these days it makes sense to start small with a container program that can evolve.  One would rather see software that acts lie a Swiss Army knife than have one use only.

The question is, how will the authors of these malware programs incorporate defense into a program with a static framework, but that gets updated with new features and goals?  We shouldn't be left with a feeling of confidence that we can identify these programs more easily knowing the codebase will have some static elements to it.  In fact, this should be of concern as it is indicative of programming sophistication, long-term goals and commitment to the crimes being executed through the software.

Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Google's new See No Evil policy......
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
How Enterprises are Developing Secure Applications
How Enterprises are Developing Secure Applications
Recent breaches of third-party apps are driving many organizations to think harder about the security of their off-the-shelf software as they continue to move left in secure software development practices.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 44741ff99f7a71df45420635b238b9c22093647a contains a buffer overflow which could allow attackers to obtain sensitive information.
PUBLISHED: 2021-06-18
SerenityOS contains a buffer overflow in the set_range test in TestBitmap which could allow attackers to obtain sensitive information.
PUBLISHED: 2021-06-18
SerenityOS in test-crypto.cpp contains a stack buffer overflow which could allow attackers to obtain sensitive information.
PUBLISHED: 2021-06-18
SerenityOS before commit 3844e8569689dd476064a0759d704bc64fb3ca2c contains a directory traversal vulnerability in tar/unzip that may lead to command execution or privilege escalation.
PUBLISHED: 2021-06-18
RIOT-OS 2021.01 before commit 85da504d2dc30188b89f44c3276fc5a25b31251f contains a buffer overflow which could allow attackers to obtain sensitive information.