Skip to main content

Vodafone India privacy problem: exposes phone numbers

Vodafone India is exposing website surfer/user's phone number to the partner website when using mobile data plan. It might be offering hidden API to those partner websites to uniquely identify users. I have noticed it around 1-year before, thought about blogging, but forgot it at that time. Now, I have got some time and so thought of explaining the issue.

How I noticed the issue?

Sometime ago, I've bought SanDisk microSD card. In the wrapper, they've mentioned about some offer about hungama (Still available in SanDisk website at www.sandisk.in/campaign/landing/hungama/offer_three). The URL mentioned was offers.hungama.com/sandisk3/ and when I opened that in my mobile browser, it was prompting with Welcome, 91-98XXXXXXXX.
Phone number leaked by Vodafone India


I was shocked as I never seen anything like that before. So, I immediately opened the same URL in my desktop browser and got completely different page:
Desktop version of the same page

And, again I tried to open the same page in mobile browser with Wi-Fi alone (by disabling Mobile Data), and now also they couldn't identify my mobile number. So, I realized that it might be something to do with the network (Vodafone). Initially I thought that they may be decoding the phone number from IP address. So, I asked Heleena (my wife) to figure out some pattern for that. Then it turn out that there is no definite pattern. I have also analyzed HTTP headers when browsing through Vodafone internet. Then, realized that hungama might be utilizing some hidden API from Vodafone to decode user's IP to mobile number.

Privacy Issue


At least for me, this looks like a serious privacy issue. hungama at least openly exposes the phone number to users, so that users can know that hungama can read their numbers/identity. But, there may be many sites--especially many social media sites such as Facebook, Twitter, Google, etc may still be uniquely identifying users without revealing it at all. 

Comments

Ohmkumar said…
Hi Rajesh,
Welcome back :)

Hope you agree, nothing is private in online...

Popular posts from this blog

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...

Update[1]: Zend PHP Certification – Economic Indian Price

As I blogged earlier , the Zend PHP Certification price is too high to afford in India and I contacted Daniel Kushner, Director of Education Zend Technologies Ltd. Recently Daniel Kushner and Idan Zuckerman (Zend) informed me that they're working with Pearson to fix the Indian price. In the meantime they said that they could offer me a voucher for 120 USD (original price is 200 USD). Though now I can afford to 120 USD, it is still high (MCP costs only 50 USD) for any Indian PHP guys. Anyway, I think it's a great improvement and I really applaud their efforts. I have planned to get the voucher after 1-month time though it has 6-month validity—as I have to prepare for the exam first. I have also been asked to refer friends and colleagues for this 120 USD offer. If you want to avail this offer, please buzz me (only India based PHP guys).

I'm Zend (PHP 5) Certified Engineer:-)

As of January 13, 2007, I'm ZCE/ Zend Certified Engineer (PHP 5)