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.

ABTV

1/13/2020
10:00 AM
Larry Loeb
Larry Loeb
Larry Loeb
50%
50%

Despite Google's Efforts, Bread Isn't Toast

The authors of the Bread malware have proven themselves to be unrelenting in their efforts to avoid being first discovered by and then dumped from Google's Play Store.

The Bread malware for Android is also called Joker. But no matter the name, its authors have proven themselves to be unrelenting in their efforts to avoid being first discovered by and then dumped from Google's Play Store.

Alec Guertin and Vadim Kotov, of the Android Security & Privacy Team, blogged recently about the extended conflict between the two parties that has been going on since 2017.

Bread/Joker began with one specific fraud method in mind (SMS billing) and then changed to toll fraud. SMS fraud gets a victim to pay for unwanted products or services by messaging to a specific number via SMS.

Bread changed its method of fraud after Google introduced new policies that restricted use of the SEND_SMS permission by an app.

Toll fraud connects to malicious payment pages through a device's WAP connection. The payment is then automatically charged to a device's phone bill.

Google notes the underlying problem that can be exploited by the threat actors when it explains in the blog that "Both of the billing methods provide device verification, but not user verification. The carrier can determine that the request originates from the user's device, but does not require any interaction from the user that cannot be automated. Malware authors use injected clicks, custom HTML parsers and SMS receivers to automate the billing process without requiring any interaction from the user."

The malware authors employed many differing programming techniques to try and sneak the malware past the defenses of the Play store. Not only that, as soon as one version was removed they tried to send a new and slightly different version of the malware.

Google says with some exasperation that, "At peak times of activity, we have seen up to 23 different apps from this family submitted to Play in one day. At other times, Bread appears to abandon hope of making a variant successful and we see a gap of a week or longer before the next variant. This family showcases the amount of resources that malware authors now have to expend."

Google found the authors tried "versioning" to a great extent, an abuse tactic that is unique to app stores. They saw that some apps started with clean versions, in an attempt to grow user bases and build the developer accounts' reputations. The user is unaware of the potential for fraud in the clean version, since it does not happen.

At some point, the malicious is code introduced through an update. Google found that some of the early "clean" versions would contain varying levels of signals that the updates will include malicious code at a later point.

Google's effort against Bread have stopped 1,700 apps from being downloaded by users according to their figures.

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 8/14/2020
Lock-Pickers Face an Uncertain Future Online
Seth Rosenblatt, Contributing Writer,  8/10/2020
Hacking It as a CISO: Advice for Security Leadership
Kelly Sheridan, Staff Editor, Dark Reading,  8/10/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
7 New Cybersecurity Vulnerabilities That Could Put Your Enterprise at Risk
In this Dark Reading Tech Digest, we look at the ways security researchers and ethical hackers find critical vulnerabilities and offer insights into how you can fix them before attackers can exploit them.
Flash Poll
The Changing Face of Threat Intelligence
The Changing Face of Threat Intelligence
This special report takes a look at how enterprises are using threat intelligence, as well as emerging best practices for integrating threat intel into security operations and incident response. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-17475
PUBLISHED: 2020-08-14
Lack of authentication in the network relays used in MEGVII Koala 2.9.1-c3s allows attackers to grant physical access to anyone by sending packet data to UDP port 5000.
CVE-2020-0255
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2020-10751. Reason: This candidate is a duplicate of CVE-2020-10751. Notes: All CVE users should reference CVE-2020-10751 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidenta...
CVE-2020-14353
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-18270. Reason: This candidate is a duplicate of CVE-2017-18270. Notes: All CVE users should reference CVE-2017-18270 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidenta...
CVE-2020-17464
PUBLISHED: 2020-08-14
** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
CVE-2020-17473
PUBLISHED: 2020-08-14
Lack of mutual authentication in ZKTeco FaceDepot 7B 1.0.213 and ZKBiosecurity Server 1.0.0_20190723 allows an attacker to obtain a long-lasting token by impersonating the server.