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.

Mobile

11/24/2020
05:00 PM
50%
50%

Baidu Apps Leaked Location Data, Machine Learning Reveals

Several apps available on the Google Play Store, including two made by Chinese Internet giant Baidu, leaked information about the phone's hardware and location without the user's knowledge, research finds.

Two popular apps from Baidu collected data on Android phones and uploaded it to the Internet, potentially allowing the apps to track the user, network security firm Palo Alto Networks stated in an analysis of the apps published on Nov. 24.

The Baidu Search Box and Baidu Maps applications, which have more than 6 million downloads from the US Google Play Store, both collected a variety of device identifiers from the phone on which the applications were installed. A third application, Homestyler - Interior Design & Decorating Ideas, also used a software development kit (SDK) that collects information on the user's device, according to the security firm's researchers.

Related Content:

Malicious Android Apps Slip Through Google Play Protection

The Changing Face of Threat Intelligence

New on The Edge: We Secured the Election. Now How Do We Secure Trust in Results?

The data collection did not appear to be malicious, just bad practice, says Jen Miller-Osborn, deputy director of threat intelligence for the Unit 42 research group at Palo Alto Networks.

"That kind of data can be used to track a person [and] establish location data points," she says. "It is not the data that people want to have collected on them without their knowledge."

Mobile apps leaking sensitive data has become a common problem. In one study published in May, researchers from Comparitech found 0.83% of the more than half million Android apps analyzed had errors in their database configurations, exposing sensitive user data. Extrapolating the findings across the Google Play Store suggests that some 24,000 applications leaked information

In March, security firm Check Point Software Technologies found 56 applications downloaded more than a million times from the Google Play Store contained malware, dubbed Tekya, that mimicked the user and clicked on ads and banners to generate revenue for the adware operators. 

"Although Google has taken steps to secure its Play store and stop malicious activity, hackers are still finding ways to infiltrate the app store and access users' devices," the researchers stated in a blog post. "Millions of mobile phone users have unintentionally downloaded malicious apps that have the ability to compromise their data, credentials, emails, text messages, and geographical location."

In the latest privacy incident, Palo Alto Networks' Unit 42 researchers found that Baidu's Android Push SDK was collecting and communicating unique identifiers from the mobile devices on which applications ran. While some information — such as the device model, carrier, screen resolution, and network — may not give away too much information, the SDK also collected the MAC address and the International Mobile Subscriber Identity (IMSI) number, which is unique for each person.

The IMSI and the International Mobile Equipment Identity (IMEI) numbers are both sensitive identifiers that can be used by cybercriminals to pose as the subscriber or the device, the researchers stated. 

"Once this data is acquired, cybercriminals can profile users and further extract sensitive information about them," they said in the blog post. "For example, if a cybercriminal gets hold of a phone's IMEI number, they could use it to report the phone as stolen and trigger the provider to disable the device and block its access to the network."

Palo Alto Networks researchers detected the surreptitious data collection using a machine learning component of a spyware detection tool, the company said.

The Google Play Store represents a lucrative target for any malware or spyware author. A malicious app that successfully escapes detection can garner millions of downloads in short order. 

Overall, two-thirds of malicious apps come from the Google Play Store, while 10% come from alternative third-party markets, according to researchers from NortonLifelock. Far from indicating the level of malicious apps in the Google Play Store, the data just underscores the dominance of Google's first-party position in the mobile ecosystem. The researchers found that the ratio of bad applications to legitimate ones was much better on the Google Play Store, 0.6%, compared with other sources, such as alternative third-party markets, which have a 3.2% chance of sourcing unwanted software.

"[U]nwanted app developers have a large incentive to make their apps appear in the Play market since it provides the apps with higher visibility, reputation, and trust," the researchers said. "This leads to a low fraction, but large number overall, of unwanted apps being able to bypass Play's defenses."

Google removed all three apps from the Play Store on Oct. 28, although Baidu fixed the Search Box app and it has since been reposted. Baidu Maps is still not available, according to Palo Alto Networks. Google's Android team acknowledged Palo Alto in a statement on the issue. 

"We appreciate the work of the research community, and companies like Palo Alto Networks, who work to strengthen the security of the Play Store. We look forward to collaborating with them on more research in the future," the team stated in the Palo Alto blog post.

 

Veteran technology journalist of more than 20 years. Former research engineer. Written for more than two dozen publications, including CNET News.com, Dark Reading, MIT's Technology Review, Popular Science, and Wired News. Five awards for journalism, including Best Deadline ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
NSA Appoints Rob Joyce as Cyber Director
Dark Reading Staff 1/15/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
2020: The Year in Security
Download this Tech Digest for a look at the biggest security stories that - so far - have shaped a very strange and stressful year.
Flash Poll
Assessing Cybersecurity Risk in Today's Enterprises
Assessing Cybersecurity Risk in Today's Enterprises
COVID-19 has created a new IT paradigm in the enterprise -- and a new level of cybersecurity risk. This report offers a look at how enterprises are assessing and managing cyber-risk under the new normal.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-22847
PUBLISHED: 2021-01-22
Hyweb HyCMS-J1's API fail to filter POST request parameters. Remote attackers can inject SQL syntax and execute commands without privilege.
CVE-2021-22849
PUBLISHED: 2021-01-22
Hyweb HyCMS-J1 backend editing function does not filter special characters. Users after log-in can inject JavaScript syntax to perform a stored XSS (Stored Cross-site scripting) attack.
CVE-2020-8567
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver Vault Plugin prior to v0.0.6, Azure Plugin prior to v0.0.10, and GCP Plugin prior to v0.2.0 allow an attacker who can create specially-crafted SecretProviderClass objects to write to arbitrary file paths on the host filesystem, including /var/lib/kubelet/pods.
CVE-2020-8568
PUBLISHED: 2021-01-21
Kubernetes Secrets Store CSI Driver versions v0.0.15 and v0.0.16 allow an attacker who can modify a SecretProviderClassPodStatus/Status resource the ability to write content to the host filesystem and sync file contents to Kubernetes Secrets. This includes paths under var/lib/kubelet/pods that conta...
CVE-2020-8569
PUBLISHED: 2021-01-21
Kubernetes CSI snapshot-controller prior to v2.1.3 and v3.0.2 could panic when processing a VolumeSnapshot custom resource when: - The VolumeSnapshot referenced a non-existing PersistentVolumeClaim and the VolumeSnapshot did not reference any VolumeSnapshotClass. - The snapshot-controller crashes, ...