1. Home
  2. Techie Held For Hacking Air India Frequent Flyers Accounts

Techie Held For Hacking Air India Frequent Flyers Accounts

[email protected] (Agencies)
July 18, 2016

New Delhi, Jul 18: A 23-year-old techie has been arrested for hacking Air India's Frequent Flyer member accounts and using them to book tickets sold to several travel agents, Delhi Police said on Sunday.

airindiaThe accused, Anitesh Giri Goswami, a BCA graduate from Pune, was arrested from Jaipur on Friday.

According to police, a complaint was received in the Cyber Crime Cell of the Delhi Police's Economic Offences Wing (EOW) alleging some persons were selling Air India tickets by redeeming of miles of genuine Flying Returns Members after hacking the Frequent Flyer members account.

In a statement, the EOW said it was found that the hub of the scam was in Rajasthan's Jodhpur and Anitesh was its mastermind. On basis of electronic surveillance and information of a local informer, a raid was conducted at an apartment in Jaipur and Anitesh was nabbed.

A laptop, several mobile phones and other relevant documents were also recovered from his possession.

Police further claimed that Anitesh was an IT expert, who had earlier worked with Kingfisher Airlines and Air India and was well versed with the online ticket-booking system and functioning of Air India's intranet and internet-based systems.

Explaining the modus operandi, police said that Anitesh first understood functioning of the ticketing system as well as the points/miles system of the airlines and then hacked into the Loyalty Plus programme website of Air India.

After gaining access, he administrator user rights, which he used to upgrade several other user IDs with the same rights, police said.

Using these IDs, he verified hundreds of dormant accounts of Frequent Flyer members by uploading fraudulently prepared KYC (know your customer) documents, and used these membership accounts and the miles or points accumulated in these accounts for booking airline tickets. These were sold to various travel or ticketing agents based in Pune, Delhi, Jaipur and Mumbai.

He gained access to the internal functioning of Air India website while working at the Jodhpur airport, and left his Air India job to start exploiting loopholes in the Frequent Flyer Programme's functioning.

Comments

Suresh
 - 
Monday, 18 Jul 2016

May be brother of arnab!!

Ahmed Ali K
 - 
Monday, 18 Jul 2016

Both Go-Swamis are jokers and talk of the town now a days

Add new comment

About text formats
  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
coastaldigest.com news network
August 8,2020

Mangaluru, Aug 8: As visuals of the Air India Express flight crash at Kozhikode international airport emerge, one cannot help but be reminded of an eerily similar and unfortunate accident that occurred a decade ago. The August 7, 2020 tragedy brought back memories of the 2010 crash.

It was on May 22, 2010 that an Air India Express Boeing 737-800 flight from Dubai to Mangaluru over shot the runway while landing at Bajpe airport and fell into a cliff. Of the 160 passengers and 6 crew members on board, 158 were killed (all crew members and 152 passengers) and only 8 survived.

Even back then, the plane had split into two. The crash has been termed as one of India's worst aviation disasters.

The final conversations between Air traffic control (ATC) and the pilot prior to the landing showed no indication of any distress.

Like the Mangaluru accident, Karipur crash too happened when the flight was attempting to land.

The captain of the aircraft which crashed at Mangaluru, Z Glucia, was an experienced pilot with 10,000 hours of flying experience and had 19 landings at the Mangalore airport. Co-pilot S S Ahluwalia, with 3,000 hours of flying experience had as many as 66 landings at this airport. Both the pilot and co-pilot were among the victims.

An investigation into the accident later found that the cause of the accident was the captain’s failure to discontinue an ‘unstabilised approach’ and his persistence to continue with the landing, despite three calls from the First Officer to ‘go-around’.

Comments

Add new comment

About text formats
  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
June 14,2020

Mumbai, Jun 14: Bollywood actor Sushant Singh Rajput committed suicide on Sunday, leaving all his fans and the industry in shock. While the reason behind him taking up the extreme step is still not clear, a look into Sushant’s social media feed suggests that things were not well for him for quite some time.

Sushant had been inactive on Twitter since months. His last tweet was on December 27, 2019. Since then, he did not even reply to any one on Twitter. Same is the case with his Facebook account as the last post on his timeline was on the same date. Interestingly, Sushant's Twitter cover picture is the popular painting - 'Starry Night', by Van Gogh, who had also reportedly committed suicide in 1890.

On Instagram, the young actor had last posted on June 3. It was a collage picture of him and his mother along with a cryptic caption that read, “Blurred past evaporating from teardrops Unending dreams carving an arc of smile And a fleeting life, negotiating between the two...#माँ”.

Was Sushant’s inactivity on Twitter, Facebook and his last cryptic post on Instagram a signal that the actor was having a tough time? Well, may be it will remain a mystery forever.

Comments

Add new comment

About text formats
  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.
News Network
February 14,2020

Bengaluru, Feb 14: BJP leader and Karnataka Revenue Minister R Ashok refused to comment on the Bellary car accident case, allegedly involving his son, saying that the matter was still under investigation and that they did not have anything to do with the said car.

The car crash took place on February 10, when a speeding red Mercedes Benz allegedly driven by Ashok's son rammed into a tea stall by the roadside killing two people. While a 16-year-old boy Ravi died on the spot, one of the car's passengers was also killed in the accident.

"I came to know about the incident and also heard that two people have died and a few others have sustained injuries. Everybody is equal under the law. It is not fair to comment as a minister when the case is being investigated," Ashok told reporters here on Thursday.

However, the minister avoided answering questions about his son's presence in the car and said that they had "no connection" with the car.

"The case is in the investigation stage, I don't want to comment on anything. My son's name is not present in the FIR. We have no connection with the car," he said.

Superintendent of Police CK Baba told reporters that Ashok's son was not present in the car.

"There was no senior BJP leader and Revenue Ministers's son in the car. We will not hide anything and the case will be investigated," Baba said.

Comments

Add new comment

About text formats
  • Coastaldigest.com reserves the right to delete or block any comments.
  • Coastaldigset.com is not responsible for its readers’ comments.
  • Comments that are abusive, incendiary or irrelevant are strictly prohibited.
  • Please use a genuine email ID and provide your name to avoid reject.