Ticketmaster Suffer Huge Data Breach

Ticketmaster have been hacked in breaking news today. Alongside the BBC, their sensitive data is at risk on hundreds of millions of users. This blog highlights what happened, how it happened and what you can do to protect yourself if you think you may be affected.

What Happened? 

Ticketmaster appears to have suffered a huge data breach, causing it to lose sensitive data on hundreds of millions of users.

A report from Hackread claims a group known as ShinyHunters published a 1.3TB database of compromised customer data, on the newly-reopened BreachForums criminal site.

The database contained sensitive information on 560 million users, including payment data, but also containing people’s names, postal addresses, email addresses, phone numbers, ticket sales and event details, order information, and even partial payment card data, for sale. The partial payment card data includes cardholder names, the last four digits of the cards, expiration dates, and some customer fraud details.

What Ticketmaster Data was Stolen?

In the Ticketmaster data breach, sensitive user data was stolen, including full names, addresses, phone numbers, email addresses, and order history information. The breach also involved the theft of partial payment data.

Firstly, the stolen data included users' full names, enabling the attackers to have complete identification details. Along with this, addresses were compromised, potentially exposing users' physical locations and personal residences. Phone numbers were also stolen, allowing for potential harassment or unsolicited communication.

Moreover, email addresses were part of the stolen data, which can lead to phishing attempts or further targeted attacks. This can result in users falling victim to scams or having their email accounts compromised. Additionally, the breach exposed users' order history information, providing the attackers with insights into the users' previous purchases.

Furthermore, the breach involved the theft of partial payment data, which poses an additional risk to affected users. Though it is not specified what partial payment data was stolen, possible examples include credit card numbers or bank account details. This can lead to financial fraud and unauthorised transactions.

How Did This Happen?

In an ever-evolving world driven by technology and constant connectivity, it seems almost unfathomable that certain events occur, leaving us perplexed and questioning "how did this happen?". Whether it be a shocking turn of events, a sudden and unexpected outcome, or a series of circumstances that seem impossible to unravel, the question of how such occurrences come to pass remains a tantalizing puzzle. It is through exploration, analysis, and understanding that we can begin to unravel the complexity behind these seemingly inexplicable happenings, unraveling the threads of causation and shedding light on the factors that contributed to their occurrence. By delving into the underlying causes, we may discover hidden connections, human error, systemic flaws, or even the impact of larger sociopolitical factors, ultimately providing valuable insight into how this seemingly improbable event came to be. So, let us embark on a journey of investigation as we seek to uncover the origins and forces at play behind these perplexing occurrences, attempting to answer the enduring question of how they happened.

Reputational Damage Likely

Ticketmaster should take immediate steps to address the likely reputational damage caused by the breach. Firstly, it is crucial for Ticketmaster to demonstrate transparency in their response to the breach. They should openly communicate with their customers, stakeholders, and the public, providing clear and timely information about the breach, the extent of the damage, and the steps being taken to mitigate it. This transparency will help build trust and show accountability for what has happened.

Additionally, Ticketmaster should offer support services to affected customers. This could include dedicated helplines, online resources, and assistance in addressing any potential financial or identity theft issues. By providing support services, Ticketmaster can demonstrate their commitment to helping customers through the aftermath of the breach and minimize any potential harm caused.

Ticket to Hide

Ticketmaster, the online ticket sales and distribution company, has suffered from multiple security breaches over the years. One of the most notable incidents occurred in 2018, when hackers managed to infiltrate the company's systems and steal personal data of its customers.

During this breach, sensitive information, including names, addresses, payment details, and login credentials, were exposed. The stolen data could potentially be used for malicious purposes, such as identity theft and fraud.

Following the personal data theft, Ticketmaster also faced a subsequent hack attack. This attack involved the use of malicious software, known as Magecart, which was capable of stealing payment information entered by customers during the online checkout process. The hackers injected the malware into a third-party chatbot, which was integrated into Ticketmaster's website.

Data Breaches Impact Major Corporations

Data breaches continue to have a significant impact on major corporations, with a considerable prevalence among such companies. Several recent examples, like the data breaches on Dell and Ticketmaster, underscore the severity of this issue.

Dell, a multinational technology company, experienced a data breach in 2020 that compromised sensitive customer information. The breach, resulting from an unauthorized party gaining access to Dell's online support domain, exposed names, email addresses, and hashed passwords of its customers. Similarly, Ticketmaster, a prominent ticket sales and distribution company, suffered a data breach in 2018 caused by malicious software. This breach allowed unauthorized access to personal and payment information of millions of customers.

The latest reports by Verizon and Nuspire emphasize the alarming increase in vulnerability exploitation and attempted exploits. Verizon's Data Breach Investigations Report (DBIR) highlights that data breaches remain a persistent threat across industries, affecting major corporations as well. The comprehensive study reveals that 36% of data breaches in 2021 involved large organisations, reiterating the prevalence of such incidents among major companies.

What Data was Leaked?

In the Ticketmaster breach, a significant amount of data was compromised, including both credit card information and personal information of customers. Credit card data that was leaked included card numbers, expiration dates, and security codes, posing a serious risk for potential fraudulent activities. In addition, the breach exposed sensitive personal information, such as billing addresses, cardholder names, full names, addresses, phone numbers, and email addresses, which could be exploited for identity theft or spamming purposes. Furthermore, the leaked data encompassed extensive order history information, providing attackers with insights into customers' purchasing behaviors, preferences, and patterns. This breach also compromised ticket purchase details, potentially revealing the specific events that customers attended or planned to attend. The leaked Ticketmaster event information could further affect customers' privacy and security as it discloses their interests, preferences, and potentially their social activities. The breach highlights the critical importance of safeguarding personal and financial data with robust security measures to prevent such disruptions and protect customer trust.

How was Ticketmaster Hacked?

In 2018, Ticketmaster suffered a major data breach resulting from a cyber attack. The incident involved the compromise of a third-party customer support provider, Inbenta Technologies, which was used by Ticketmaster. Hackers implanted malicious software into Inbenta's code, allowing them to gain unauthorized access to Ticketmaster's data.

The data breach affected Ticketmaster's UK customers specifically. It is estimated that around 40,000 customers were affected by the attack. The breach occurred between February and June 2018, during which the hackers were able to access and steal customers' personal information.

The types of information that were compromised during the breach include names, email addresses, phone numbers, addresses, and limited payment details. This means that the hackers had access to customers' personal and financial information, including credit card details.

Once the breach was discovered, Ticketmaster immediately launched an investigation. They brought in forensic teams and security experts to assess the extent of the breach, secure their systems, and mitigate any potential damage. Affected customers were advised to monitor their bank statements for any suspicious activity and to consider changing their passwords.

Ticketmaster's Solution

In response to the data breach, Ticketmaster implemented a comprehensive solution to address the issue and enhance the security of its platform. Firstly, immediate measures were taken to secure the platform by strengthening the existing infrastructure and implementing additional security measures. This included reinforcing firewalls, updating intrusion detection systems, and enhancing encryption protocols to protect user data.

To remove the malicious software, Ticketmaster worked closely with cybersecurity experts. Their expertise was utilized to identify and eliminate any traces of unauthorized access, as well as to implement advanced threat detection and prevention systems. Regular audits and vulnerability assessments were also conducted to ensure the ongoing security of the platform.

To notify affected customers, Ticketmaster promptly sent out notification emails, informing them about the data breach and the steps taken to address the issue. The emails emphatically urged customers to change their passwords to enhance account security. Additionally, Ticketmaster provided detailed instructions on how to reset passwords and advised users to choose strong, unique passwords.

How Do I Know If I Was Affected?

If you're concerned about whether or not you were affected by the Ticketmaster data breach, there are a few steps you can take to determine if your information was compromised. Firstly, Ticketmaster has notified customers believed to be affected by the breach. So, the first thing you should do is check if you received any notification from Ticketmaster regarding the incident.

If you haven't received a notification from Ticketmaster, it's still important to ensure your data is secure. One way to check if your credentials have been compromised is by visiting a website called "Have I Been Pwned." This website allows you to enter your email address and will inform you if it has been associated with any known data breaches, including the Ticketmaster breach.

By following these steps, you can determine if you were affected by the Ticketmaster data breach. Stay vigilant and make sure to regularly check for any notifications from Ticketmaster or other trusted sources to ensure the safety of your personal information.

What Should Affected Users Do?

Affected users should take the following steps to address the security breach:

1. Change Password: The first step is to immediately change the password associated with the affected Ticketmaster account. Choose a strong and unique password to ensure maximum security.

2. Reset Passwords for Other Accounts: If the same password was used for other accounts, it is crucial to reset passwords for those accounts as well. Reusing passwords increases the risk of unauthorised access to multiple accounts.

3. Enable Two-Factor Authentication: Enhance account security by enabling two-factor authentication (2FA) where available. This adds an extra layer of protection by requiring a verification code in addition to the password.

4. Monitor Accounts: Regularly monitor all linked accounts for any suspicious activity, such as unauthorized transactions or login attempts. Report any suspicious activity immediately to the respective service providers.

5. Contact Ticketmaster Help: If affected users have specific concerns or questions about the breach, it is advised to contact Ticketmaster Help for guidance and assistance. They can provide further information about the incident and steps to mitigate the impact.

6. Check Credentials on "Have I Been Pwned": Affected users should visit the website "Have I Been Pwned" and enter their email address to check if their credentials have been compromised in any other data breaches. This will help identify potential risks and take appropriate action.

By following these steps, affected Ticketmaster users can proactively protect their accounts and minimise the impact of the security breach.

Securing your digital assets is crucial to stop data breaches. DarkInvader has a feature as part of its External Attack Surface Monitoring that allows users to upload their assets to gain unique information on any vulnerabilities that affect them specifically.

Secure your digital assets and get in touch today with DarkInvader.

blog

Related articles

Breaking News: More than 200 ‘life-saving’ operations cancelled by NHS hospitals after cyberattack

June 12, 2024

Read

Ticketmaster Suffer Huge Data Breach

May 30, 2024

Read

When Hackers Expose Cheaters: Ashley Madison Data Leak

May 24, 2024

Read

AT&T Data Breach: Millions of Customers Caught up in Major Dark Web Leak

April 12, 2024

Read

BREAKING NEWS: LockBit Ransomware Takedown

February 22, 2024

Read

What to do if Your Email is on the Dark Web?

February 9, 2024

Read

An Introduction to AI-based Audio Deep Fakes

February 8, 2024

Read

Apprenticeship Journey's at DarkInvader

February 5, 2024

Read

Deep Vs. Dark Web: What's the Difference?

January 24, 2024

Read

Open Source Intelligence for External Attack Surface Management

January 23, 2024

Read

What is Typo Squatting?

January 15, 2024

Read

How IT Teams Can Identify Unknown Public Attack Vectors Through OSINT Gathering

January 11, 2024

Read

Why Should Businesses Scan The Dark Web?

January 9, 2024

Read

What is a Dark Web Scan?

January 8, 2024

Read

The Role of Domain Security in Phishing Prevention

January 4, 2024

Read

Unveiling The Positive Potential of The Dark Web

January 3, 2024

Read

How Threat Actors Choose Their Victims

December 21, 2023

Read

The Problem with Social Media and the Risk in 2024

December 20, 2023

Read

Unmasking Threat Actors: Safeguarding Your Business in the Digital Battlefield

December 19, 2023

Read

Risk Mitigation Strategies for Modern IT Teams

December 4, 2023

Read

The Crucial Role of Vulnerability Management in External Attack Surface Management

November 29, 2023

Read

How to Detect and Respond to Dark Web Threats?

November 23, 2023

Read

A Guide for Executives Faced with Cyber Extortion

November 22, 2023

Read

Why External Attack Surface Management is Important in Today's Digital Landscape

November 13, 2023

Read

How Deploying an EASM Solution Strengthens Your Security Posture

November 8, 2023

Read

Enhancing Cyber Defence: The Role of External Attack Surface Management

October 26, 2023

Read

The Imperative of Monitoring the Dark Web: Protecting Our Digital World

October 26, 2023

Read

10 Ways to Protect Your Online Identity

October 18, 2023

Read

Navigating Cybersecurity Breaches: Lessons from Sony’s Recent Incident

October 16, 2023

Read

What is Human Attack Surface?

September 25, 2023

Read

OSINT Tools & Techniques

September 12, 2023

Read

What is Quantum Computing?

September 12, 2023

Read

Dark Web Forums Vs Illicit Telegram Groups

August 18, 2023

Read

What is Attack Surface Mapping?

August 10, 2023

Read

LockBit Ransomware Gang

July 31, 2023

Read

What is The Dark Web?

July 24, 2023

Read

The Cyber War - Russia & Ukraine

July 17, 2023

Read

Attack Surface Reduction Rules (ASRR)

June 30, 2023

Read

Protecting Your Digital Identity: Essential Cybersecurity Practices

June 23, 2023

Read

Whistle Blowing & The Art of Online Privacy

June 21, 2023

Read

How Does Attack Surface Management Work?

June 16, 2023

Read

Why is Attack Surface Management Important?

June 13, 2023

Read

Cyber Criminals: Being Anonymous Online

June 12, 2023

Read

Exploring The Deep Web and Debunking Myths

June 7, 2023

Read

New Ransomware Group: Akira Ransomware

May 23, 2023

Read

New Form of AI: Deep Fakes

May 23, 2023

Read

Capita Hack

May 19, 2023

Read

The Monopoly Market Attack

May 17, 2023

Read

The DarkInvader Insider Video

May 15, 2023

Read

New Ransomware Strain ‘CACTUS’ Exploits VPN Flaws to Infiltrate Networks

May 12, 2023

Read

Chat GPT - What Happened?

May 11, 2023

Read

Dark Pink APT Group Deploys KamiKakaBot Against South Asian Entities

May 10, 2023

Read

Black Basta Cyber Attack Hits Capita

April 25, 2023

Read

Genesis Market and Breached Website Shut Down

April 17, 2023

Read

3CX Attack - What Happened?

April 14, 2023

Read

How Geopolitical Tensions Impact Cyber Security

April 12, 2023

Read

How to Detect and Respond to Dark Web Threats?

April 3, 2023

Read

What is Threat Intelligence?

March 29, 2023

Read

'TikTok Due to be Blocked From Parliamentary Devices and Network Over Cyber Security Fears'

March 27, 2023

Read

How Can Hackers Destroy Your Business?

March 23, 2023

Read

Top Emerging Cyber Threats for Businesses in 2023

March 20, 2023

Read

How Can Wide Digital Intelligence Overcome Challenges to Solve Crypto Crimes?

March 6, 2023

Read

DarkNet Drug Markets - Breakdown

March 2, 2023

Read

Dark Web Market Revenues Sink 50% in 2022

February 20, 2023

Read

Are Cyber Criminals Offering Jobs on The Dark Web?

February 10, 2023

Read

ThreatBites 08: Dark Web Stories & Forums

January 31, 2023

Read

Why Has There Been a Recent Spike in Ransomware Attacks

January 24, 2023

Read

A Glimpse Into the Dark Web: What You Can Find In the Marketplaces and Forums

January 9, 2023

Read

Why Should Businesses Actively Search for Threats?

December 20, 2022

Read

ThreatBites 06 - Christmas Cyber Scams

December 2, 2022

Read

ThreatBites 05 - Improving Phishing Campaigns with OSINT

November 23, 2022

Read

ThreatBites 04 - The Effects of GDPR on OSINT

November 11, 2022

Read

ThreatBites 03 - Credential Stuffing

November 7, 2022

Read

ThreatBites 02 - Technical Threats

November 4, 2022

Read

ThreatBites 01 - OSINT Overview

November 4, 2022

Read

The Ultimate Guide to OSINT and Google Dorking

October 17, 2022

Read

It’s Time to Update Your Privacy Settings

October 14, 2022

Read

OSINT and Technical Threats: The Shift in Peoples Threat Landscapes and the Increase in Ransomware Attacks

October 5, 2022

Read

Discover What Threat Intelligence Is and Why its Crucial

October 5, 2022

Read

Introduction to Open Source Intelligence Gathering (OSINT)

September 8, 2022

Read

Why Should you Monitor the Dark Web?

September 8, 2022

Read

Is it Illegal to Browse the Dark Web?

September 8, 2022

Read

What Makes DarkInvaders DarkWeb Scanning Superior?

September 7, 2022

Read

How are Hackers Using the Dark Web to Attack Businesses?

September 7, 2022

Read

How do Credentials Leak to The Dark Web & What are The Risks?

September 7, 2022

Read

What is Dark Web Monitoring?

September 3, 2022

Read

Dark Web Monitoring Questions

August 29, 2022

Read