Incident · 8-K Item 8.01
Live Nation reports unauthorized activity in a third-party cloud database holding Ticketmaster data
Compiled from public records. Updated 2026-11-12. By the cisonews.net Desk.
Live Nation Entertainment, Inc. disclosed in a Form 8-K filed under Item 8.01 on May 31, 2024 that it identified unauthorized activity on May 20, 2024 in a third-party cloud database environment holding company data, primarily from its Ticketmaster L.L.C. subsidiary. The filing refers to personal information only in general terms and gives no count of affected people.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.
What happened at Live Nation and Ticketmaster, and when?
The company says it began an investigation once it identified the activity on May 20, 2024. Seven days later, on May 27, 2024, a criminal threat actor made an offer involving what it claimed was company user data. The filing describes this as an allegation by the seller and does not confirm that the offered data is genuine.
How did Live Nation respond?
Live Nation states that it is working to reduce risk to users and to itself. It also says that regulators and users will be notified where appropriate, without saying when or how many.
Did the breach affect Live Nation's business?
The company reports no material effect so far and does not expect one. It adds that its assessment is not finished. The company chose Item 8.01, Other Events, for this report.
How many Washington residents were affected?
Washington's attorney general lists a report from Ticketmaster LLC on June 22, 2024, for a breach dated April 2, 2024, with 500 Washingtonians affected. The information it records as compromised is: name, financial and banking information, full date of birth and passport number. That count covers Washington residents only.
What does Live Nation's annual report say?
Live Nation's annual report for 2024, filed on February 21, 2025, does not name the Ticketmaster incident in its cybersecurity section. It says instead that risks from cybersecurity threats, including any previous cybersecurity incidents, have not materially affected the company. That matches the 8-K's own view: the company did not believe the incident was reasonably likely to have a material impact on its overall operations or financial condition. The record has no 8-K/A, no count of affected people from Live Nation itself, and no cost figure. How other companies in the log closed out an incident in later reports is in After the 8-K.
What did Ticketmaster's breach letter say?
Ticketmaster began notifying customers in late June 2024. BleepingComputer quoted the letter it filed with Maine's attorney general: an unauthorized third party took information from a cloud database hosted by a third-party data services provider. The letter puts the activity between April 2 and May 18, 2024, and says Ticketmaster determined on May 23, 2024 that the reader's personal information may have been affected. It offered one year of free identity monitoring. The 8-K, by comparison, gave only the May 20 date on which the company identified the activity.
| Date | What happened | Source |
|---|---|---|
| April 2, 2024 | Start of the unauthorized activity | Ticketmaster letter (as quoted) |
| May 18, 2024 | End of the activity | Ticketmaster letter |
| May 20, 2024 | Live Nation identifies the activity | 8-K |
| May 23, 2024 | Ticketmaster determines personal information may be affected | Ticketmaster letter |
| May 27, 2024 | Criminal threat actor offers alleged user data for sale | 8-K |
| May 31, 2024 | 8-K filed | 8-K |
| June 22, 2024 | Washington record (500 residents) | Washington AG |
| Late June 2024 | Letters to customers | BleepingComputer |
Was the Ticketmaster breach part of the Snowflake attacks?
The press reported it that way. Live Nation's own filings name only "a third-party cloud database environment". BleepingComputer reported that the database was Ticketmaster's Snowflake account. It said the attackers used Ticketmaster credentials that did not have multi-factor authentication enabled. It also reported that a joint investigation by Snowflake, Mandiant and CrowdStrike tied the wave to a threat actor tracked as UNC5537. That actor used stolen customer credentials against at least 165 organizations that had not set up multi-factor authentication.
How many Ticketmaster customers were affected?
No filing gives a number. The only official count is Washington's 500. The figure most often repeated, 560 million, is the seller's claim. BleepingComputer reported that ShinyHunters began selling the data on May 28, 2024 for $500,000. The group claimed 1.3TB covering 560 million customers, ticket sales, event information, customer fraud data and partial card information. Samples BleepingComputer saw held full names, email addresses, phone numbers, addresses, hashed credit card details and payment amounts.
What is still unknown about the Ticketmaster breach?
Live Nation's filings do not name the cloud provider, list the data types, or give a count of users or countries. The letters' data list varies by reader, according to the press report, and no public filing confirms or rejects the 560 million claim. No amended 8-K is on record here, and the only state count found so far is Washington's 500.
How this disclosure's timing compares
Live Nation Entertainment disclosed 11 days after the discovery date its filing gives. Across the 22 other filings under 8-K Item 8.01 on cisonews.net that date discovery to the day, the median gap is 3 days.
The rule behind an Item 8.01 filing
Item 8.01 (Other Events) is the item the SEC's Division of Corporation Finance encouraged companies to use for a cybersecurity incident they have not yet determined to be material, or have determined is not material. Its May 21, 2024 statement says a company that later determines the incident is material should file under Item 1.05 within four business days of that decision. Source: U.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance. The guide Item 8.01 versus Item 1.05: when a cyber incident moves between them reads the rule in full, and the glossary defines Form 8-K Item 1.05.
Other hospitality & entertainment incidents on cisonews.net
- Fandango Media, LLC, Breach notice, first disclosed November 13, 2026
- Kalahari Management Co. LLC, Breach notice, first disclosed November 9, 2026
- Center Theatre Group, Breach notice, first disclosed November 3, 2026
- Sarku Japan, Breach notice, first disclosed October 27, 2026; 6,424 affected in total (Indiana Attorney General)
- Magna Hospitality Group, Breach notice, first disclosed October 13, 2026; 25,623 affected in total (Indiana Attorney General)
Sources
- 2024-05-31 · ALive Nation Entertainment, Inc., Form 8-K (SEC EDGAR), published May 31, 2024
- 2025-02-21 · ALive Nation Entertainment, Inc., Form 10-K for 2024 (SEC EDGAR), published February 21, 2025
- 2026-11-09 · AWashington State Office of the Attorney General, data breach notifications list, published November 9, 2026
- 2024-06-28 · BBleepingComputer, Ticketmaster sends notifications about recent massive data breach, published June 28, 2024
- 2024-05-21 · AU.S. Securities and Exchange Commission, statement by the Director of the Division of Corporation Finance, published May 21, 2024
Tier A: the organization itself (including notices it filed with a state attorney general), a regulator or SEC EDGAR. Tier B: established press. Each fact on this page carries its supporting passage in the page source.
Entries like this one, in Wednesday’s docket
Wednesdays
Unsubscribe any time.