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

11/2/2015
05:00 PM
Connect Directly
Twitter
RSS
E-Mail
50%
50%

Mobile Malware Makes Mobile Banking Treacherous

Kaspersky Lab report shows rate of mobile malware occurrence exploding in Q3.

The number of mobile threats percolating on devices worldwide has risen precipitously this year—over three-fold, according to a new report out by Kaspersky Lab. And though the occurrence of enterprise breaches caused by mobile devices continues to be questioned by experts, attackers do seem to be profiting from their attacks by targeting individual users’ bank accounts.

Kaspersky’s Q3 Threat Evolution report examined activity in its network of users and found an increase in the number of mobile threats, the number of mobile malware attempts at stealing from consumer bank accounts, and the number of mobile bank Trojans active in the last quarter.

“Malicious mobile programs are on the rise and in countries where online banking is popular, people are at considerable risk from Trojans looking to target them,” says David Emm, principal senior security researcher at Kaspersky Lab's Global Research and Analysis team. According to his team, last quarter they found over 1.6 million malicious mobile installation packages circulating, including 323,000 new malicious mobile programs and 2,500 mobile banker Trojans. The number of mobile banker Trojans increased four-fold in just a single quarter, making it the fastest growing category of mobile threats in the wild.

But the still undisputed king of mobile malware is malvertising, which continues to pour it on strong in volume and diversity of attacks.

"We have also observed a growing number of programs that use advertising as the main monetization method while also using other methods from the virus writers’ arsenal," Em says. "They often root the device of a victim and use superuser privileges, making it very difficult, if not impossible, to combat them. In Q3 2015, these Trojans accounted for more than half of the Top 20 most popular mobile malware."

The tried and true SMS Trojan scam also continues to proliferate, sending paid messages from infected devices without permission. Researchers report that even though its share of the mobile criminal underground is declining, its still leads in the number of new samples detected.

Ericka Chickowski specializes in coverage of information technology and business innovation. She has focused on information security for the better part of a decade and regularly writes about the security industry as a contributor to Dark Reading.  View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Threaded  |  Newest First  |  Oldest First
seo rennes
100%
0%
seo rennes,
User Rank: Apprentice
11/3/2015 | 10:08:02 AM
user lambda
I am very worried about this problem.
The average user of a mobile phone does not imagine that his phone has a real OS. They're not prepared to protect themselves against viruses on his mobile phone.
GaryM03001
50%
50%
GaryM03001,
User Rank: Apprentice
11/5/2015 | 6:38:47 PM
Trusted Apps = Mobile Malware = 1B+ Infected!
@SnoopWallSecure we've been saying this since 2013.  Here's proof:

How about a trusted flashlight app, downloaded by the hundreds of millions spying on you?


Go to finovate dot com forward slash videos forward slash finovatefindevr-2015-snoopwall and see for yourself!

It's serious and most of the big banks don't care.  They want to write it off and let you think their smartphone apps are safe - as safe as an ATM machine being SKIMMED every day!

 
News
Inside the Ransomware Campaigns Targeting Exchange Servers
Kelly Sheridan, Staff Editor, Dark Reading,  4/2/2021
Commentary
Beyond MITRE ATT&CK: The Case for a New Cyber Kill Chain
Rik Turner, Principal Analyst, Infrastructure Solutions, Omdia,  3/30/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
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
CVE-2020-24285
PUBLISHED: 2021-04-12
INTELBRAS TELEFONE IP TIP200 version 60.61.75.22 allows an attacker to obtain sensitive information through /cgi-bin/cgiServer.exx.
CVE-2021-29379
PUBLISHED: 2021-04-12
** UNSUPPORTED WHEN ASSIGNED ** An issue was discovered on D-Link DIR-802 A1 devices through 1.00b05. Universal Plug and Play (UPnP) is enabled by default on port 1900. An attacker can perform command injection by injecting a payload into the Search Target (ST) field of the SSDP M-SEARCH discover pa...
CVE-2015-20001
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.2.0, BinaryHeap is not panic-safe. The binary heap is left in an inconsistent state when the comparison of generic elements inside sift_up or sift_down_range panics. This bug leads to a drop of zeroed memory as an arbitrary type, which can result in a memory ...
CVE-2020-36317
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, String::retain() function has a panic safety problem. It allows creation of a non-UTF-8 Rust string when the provided closure panics. This bug could result in a memory safety violation when other string APIs assume that UTF-8 encoding is used on the sam...
CVE-2020-36318
PUBLISHED: 2021-04-11
In the standard library in Rust before 1.49.0, VecDeque::make_contiguous has a bug that pops the same element more than once under certain condition. This bug could result in a use-after-free or double free.