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. 
Labels:

Comments

Ohmkumar said…
Hi Rajesh,
Welcome back :)

Hope you agree, nothing is private in online...
May 1, 2016, 3:52:00 PM
Post a Comment

Popular posts from this blog

Using Sodexo Meal Pass Card in BigBasket.com - How-to

How to Use Sodexo Meal Pass Card in Bigbasket.com Sodexo started to issue Smart Card similar to Credit Card--instead of their usual paper based vouchers. I was using Sodexo vouchers for longtime, but it was a big letdown when I can't get some of my unused vouchers renewed. And so, I was somehow happy with their new Meal Pass Card. But, again, it was a big letdown as I can't use it with BigBasket--where I usually use most of my meal coupon vouchers. SMS message from Sodexo on December 20, 2017 1:18 PM came as a big surprise, as I was waiting for this for longtime: Great News! Pay with your Sodexo Meal Card for food items ordered from Big Basket. Choose Sodexo in the payment section & pay on delivery. And so, this month, I tried to use my Sodexo Meal Pass Card in BigBasket. BigBasket website had not much information; I thought that I have to swipe my Meal Pass Card. Delivery person also didn't have much information; initially he was rejecting my Card! I trie...
Post a Comment
Read more

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...
Post a Comment
Read more

Looking Back at My Predictions

People who work closely with me often appreciate my ability to anticipate trends in technology stacks. With that in mind, I recently revisited some of my old blog posts—and it turns out, many of those predictions have held true. Here are a few handpicked posts that aged well: Prediction: Expensify will crash through its insane question-based hiring process February 23, 2022 BlackLivesMatter campaign may consolidate votes for Trump June 15, 2020 Technology prediction for 2018 January 16, 2018 Node.js and client app are the future of webdeving? December 29, 2011 Yahoo! and delicious.com - What's wrong? December 19, 2010 Disclosure: The following ChatGPT prompt is used in this blog post: Please fix the language of the below text and highlight the changes in bold:
Post a Comment
Read more