BSNL, India’s largest telco breached

Well this ones worth coming back so soon for…. We just found out about the breaches and details of a hack on India’s largest telecommunications company. this hack by @ThEhACkER12 contains such a simple a exploit anyone could do it. This exploit which is by far one of the most stupid one ( on behalf of BNSL ), it allows anyone to view accounts information.

Found a big vulnerability in Bharat Sanchar Nigam Ltd (BSNL) Network. BSNL is the India’s largest, oldest & the only telecomm company in the Government sector. For hacking into system of BSNL you don’t need to be a Hacker or a computer geek, just copy paste the URL & you will be logged in as an Employee of BSNL. And the interesting part is everybody will get a chance to sneak into the system (means no matter if you change the password, if other person copy-paste the same URL he too will be directed to the accounts setting) till they fix the vulnerability. This shows how lame/corrupt is the Indian Government company’s when it comes to security even after eating Billions of Rupees of the common people. Although the intension is to expose them not harm them (Financially). It’s a war against corruption that we are fighting. Posting ‘only’ ‘some’ of the Helpdesk employee login URL’s, even though the site is highly vulnerable to just a simple SQL Injection attack. With this giving you the personal email Id’s of top most heads of the company. By ThEhACkER12 @ThEhACkER12 Enjoy the Mayhem!

Some information about BNSL: BSNL is India’s oldest and largest communication service provider (CSP). It had a customer base of 90 million as of June 2008.[6] It has footprints throughout India except for the metropolitan cities of Mumbai and New Delhi, which are managed by Mahanagar Telephone Nigam Limited (MTNL). As of June 30, 2010, BSNL had a customer base of 27.45 million wireline and 72.69 million wireless subscribers** @ThEhACkER12 has also dumped a list of vulnerable URLS and instructions how to use them, for this reason we can not link to the original leak, sorry we are not out to cause chaos.**

About the author: Lee J

Security Analyst, Developer, OSINT,

Comments are closed.