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

End of Bibblio RCM includes -->
1/13/2020
10:00 AM
Larry Loeb
Larry Loeb
Larry Loeb

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
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Improving Enterprise Cybersecurity With XDR
Enterprises are looking at eXtended Detection and Response technologies to improve their abilities to detect, and respond to, threats. While endpoint detection and response is not new to enterprise security, organizations have to improve network visibility, expand data collection and expand threat hunting capabilites if they want their XDR deployments to succeed. This issue of Tech Insights also includes: a market overview for XDR from Omdia, questions to ask before deploying XDR, and an XDR primer.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-2287
PUBLISHED: 2022-07-02
Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.
CVE-2022-34911
PUBLISHED: 2022-07-02
An issue was discovered in MediaWiki before 1.35.7, 1.36.x and 1.37.x before 1.37.3, and 1.38.x before 1.38.1. XSS can occur in configurations that allow a JavaScript payload in a username. After account creation, when it sets the page title to "Welcome" followed by the username, the usern...
CVE-2022-34912
PUBLISHED: 2022-07-02
An issue was discovered in MediaWiki before 1.37.3 and 1.38.x before 1.38.1. The contributions-title, used on Special:Contributions, is used as page title without escaping. Hence, in a non-default configuration where a username contains HTML entities, it won't be escaped.
CVE-2022-34913
PUBLISHED: 2022-07-02
** DISPUTED ** md2roff 1.7 has a stack-based buffer overflow via a Markdown file containing a large number of consecutive characters to be processed. NOTE: the vendor's position is that the product is not intended for untrusted input.
CVE-2022-2286
PUBLISHED: 2022-07-02
Out-of-bounds Read in GitHub repository vim/vim prior to 9.0.