Group Action Lawyers
Latest News & Updates

Tag: data breach

data breach cyber attack
May 27, 2019
Thousands more affected by the TalkTalk data breach

The information for thousands more victims of the 2015 TalkTalk data breach incident have been found online as the number of victims expands.

We’re representing a group of victims who are claiming for data breach compensation who were affected by the TalkTalk hack of 2015. This is one of the over 40 different group and multi-party actions we’re fighting for justice in on a No Win, No Fee basis.

If you are one of the additional 4,545 victims of the incident, or if you were notified previously and you’ve yet to start your case, make sure you contact us ASAP.

Continue Reading…

British Airways data breach compensation
September 21, 2018
British Airways data breach compensation action

We’ve launched a British Airways data breach compensation action after the revelation that the data for 380,000 payment cards has been compromised.

British Airways should have notified all victims to confirm that they’ve been affected by the breach by now. The breach period took place between 10.58pm on 21 August 2018 and 9:45pm on 5 September 2018. If you made a payment during this period, you may be affected.

The British Airways data breach compensation action is one of dozens of group action cases our lawyers are, and have been, engaged in. For help and advice now, please contact the team.

Continue Reading…

July 13, 2018
Ticketmaster data breach group action

A Ticketmaster data breach group action is on the horizon as our Group Action Lawyers have taken on a number of cases against the ticketing service for their data breach that was revealed last month.

Some 40,000 victims in the UK are thought to have been affected. Those who used the service between February 2018 and June 2018 may have had their data copied using a hacked piece of script that was reportedly not supposed to have been used for the purposes Ticketmaster were using it.

The Ticketmaster data breach was also identified and reported to the company back in April, yet nothing was done about it.

Continue Reading…