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

Save American College, Madurai

This post was written in 2008 and outdated now. For update, please check Save American College, Madurai (Update 2011) Update (2011-01-16) : Save American College, Madurai (Update 2011) I'm highly privileged to have 3 degrees (B.Sc. (Spl. Physics), PGDCA and MCA) from The American College, Madurai, South India . Unlike other "commercial" colleges, American College has given room for poor students and uplifted them. And unlike other "elite" colleges who'd give seat only for "intellectuals", American College has produced geniuses. In the recent months, the saddening thing is that the college is under divide (Principal Vs. Bishop). Here is the email I sent to alumnae lately informing about the informations that I received about the developments: Update (2011-01-16) : Save American College, Madurai (Update 2011) All: I was thinking that the " Save American College " campaign was a FUD . But, when I tried to understand the problem through my
11 comments
Read more

Magic: T.K.Vadivel Pillai is above Cyril Takayama

Recently, I have been watching Cyril Takayama 's magic show in AXN channel. That reminded me of T.K.Vadivel Pillai 's magic show in Jaya TV. I have searched Vadivel's name in Wikipedia's Indian magicians article and to my surprise, his name was not present. In my opinion, T.K.Vadivel Pillai's magic is superior than Cyril's--especially, in one show, he could tell the name of the person whom the girl was thinking. Not really sure, why T.K.Vadivel Pillai could not be as popular as Cyril. Sidenote: I'm yet to see David Blaine 's magic and I still have a gut feeling that Vadivel's would be better.
1 comment
Read more

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and
6 comments
Read more