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/3/2020
'BootHole' Vulnerability Exposes Secure Boot Devices to Attack
Kelly Sheridan, Staff Editor, Dark Reading,  7/29/2020
Average Cost of a Data Breach: $3.86 Million
Jai Vijayan, Contributing Writer,  7/29/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
Special Report: Computing's New Normal, a Dark Reading Perspective
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
The Threat from the Internetand What Your Organization Can Do About It
The Threat from the Internetand What Your Organization Can Do About It
This report describes some of the latest attacks and threats emanating from the Internet, as well as advice and tips on how your organization can mitigate those threats before they affect your business. Download it today!
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2017-18112
PUBLISHED: 2020-08-05
Affected versions of Atlassian Fisheye allow remote attackers to view the HTTP password of a repository via an Information Disclosure vulnerability in the logging feature. The affected versions are before version 4.8.3.
CVE-2020-15109
PUBLISHED: 2020-08-04
In solidus before versions 2.8.6, 2.9.6, and 2.10.2, there is an bility to change order address without triggering address validations. This vulnerability allows a malicious customer to craft request data with parameters that allow changing the address of the current order without changing the shipm...
CVE-2020-16847
PUBLISHED: 2020-08-04
Extreme Analytics in Extreme Management Center before 8.5.0.169 allows unauthenticated reflected XSS via a parameter in a GET request, aka CFD-4887.
CVE-2020-15135
PUBLISHED: 2020-08-04
save-server (npm package) before version 1.05 is affected by a CSRF vulnerability, as there is no CSRF mitigation (Tokens etc.). The fix introduced in version version 1.05 unintentionally breaks uploading so version v1.0.7 is the fixed version. This is patched by implementing Double submit. The CSRF...
CVE-2020-13522
PUBLISHED: 2020-08-04
An exploitable arbitrary file delete vulnerability exists in SoftPerfect RAM Disk 4.1 spvve.sys driver. A specially crafted I/O request packet (IRP) can allow an unprivileged user to delete any file on the filesystem. An attacker can send a malicious IRP to trigger this vulnerability.