Fandango Media, the large US online movie ticket seller, is notifying customers that an unauthorized party could reach payment card details entered on its ticketing checkout page between October 8 and 11, 2026. The company's notice, filed with the California Attorney General on November 13, says the exposed data includes card numbers, CVV security codes, expiration dates, billing ZIP codes and email addresses. Fandango has not said how many customers were affected. Neither the California filing nor any public statement from the company gives a nationwide total. Edit USA reports that a separate filing with the Vermont Attorney General the same day listed 18 Vermont residents.
What Happened
Fandango's sample notice letter is titled "Fandango – Notice of Security Incident." It says the company "became aware of an issue involving Fandango's ticketing checkout page," looked into it with outside cybersecurity specialists, and resolved it. The investigation "identified evidence that an unauthorized party could access payment card information associated with certain transactions on our checkout page from October 8-11, 2026."
The timeline, based on the filing and press coverage:
- October 8 to 11, 2026: Exposure window for checkout transactions. California's breach listing records October 8 as the breach date.
- October 30, 2026: Fandango determined which customers' information may have been affected.
- November 13, 2026: Fandango filed with the California Attorney General. Severity Daily gives the report number as sb24-632866. Edit USA and Almeida Law Group report a filing with Vermont's Attorney General on the same day.
- February 13, 2027: Last day to enroll in the free monitoring offer.
The copy of the letter hosted by California has no mailing date, according to FraudMeNot and Severity Daily. BleepingComputer says the incident affected purchases made through Fandango's official website. Fandango told customers it is "not currently aware of any fraudulent use" of the data. The company has not named an attacker, and no group has claimed the attack.
Fandango sells tickets for about 31,000 US cinema screens, including AMC, Regal and Cinemark, and also runs Rotten Tomatoes. Almeida Law Group describes it as a subsidiary of NBCUniversal, which Comcast owns.
What Was Taken
Fandango's notice lists five data elements that may have been affected:
- Payment card number
- CVV security code
- Expiration date
- Billing ZIP code
- Email address
The company says customers' first and last names, government-issued ID information, Social Security numbers and other account information were not involved.
The missing name matters less than it seems. Card number, CVV, expiry date and billing ZIP are what most online stores need to approve a purchase where the card is not physically present. A breach of stored account records usually does not include the CVV, because merchants are not allowed to keep it after a transaction is authorized. Severity Daily points out that the mix of data exposed (CVV included, name excluded) suggests the data was captured from the checkout form as it was being filled in, not taken from a database.
Fandango is offering 24 months of IDX credit monitoring and CyberScan dark web monitoring, plus managed identity theft recovery. Severity Daily and Almeida Law Group report that the package also includes an identity theft insurance policy worth up to $1,000,000. Open Class Actions found no lawsuit filed as of November 15. Almeida Law Group says it is investigating the breach.
Why It Matters
This is another sign that checkout pages are still a soft target, even at large and well-known consumer brands. The attack only had to last four days. Movie ticketing involves many small card-not-present purchases spread across a huge customer base, so even a short window can produce a lot of usable card data.
From disclosure to detection, the timeline is also worth noting. The exposure ended on October 11. Affected customers were identified on October 30, and regulators were notified on November 13, more than a month after the window closed. During that time, stolen card data with valid CVVs can be sold and used. Customers who bought from Fandango during that period are relying on their card issuers' fraud controls, not on credit monitoring. Credit monitoring does little against fraud on an existing card.
Fandango says customer names were not exposed, and fraudsters can usually work around that. Email addresses were exposed, which raises the risk of targeted phishing that uses this breach as cover, such as fake "Fandango refund" or "card verification" messages.
The Attack Technique
Fandango has not publicly said how its checkout page was compromised. Its notice only refers to "an issue involving Fandango's ticketing checkout page."
BleepingComputer reports that card skimmer code was injected into the checkout page to intercept card details as customers placed orders and send them to the attackers. Almeida Law Group says the attack "appears to have involved" web skimming. The data profile supports that reading. A CVV is collected only when a customer types it in, and in a compliant setup it is not stored afterwards. A CVV in the stolen data therefore points to capture at the moment of entry, not theft from stored records.
Some points are still unknown. The company has not said whether the malicious code was loaded through a compromised third-party script, a tampered first-party JavaScript file, or access to Fandango's web servers or content delivery setup. It also has not said whether its mobile app checkout was affected. Fandango says it has fixed the issue. No indicators of compromise have been published.
What Organizations Should Do
- Inventory and lock down every script on payment pages. Keep an approved list of every script that loads on checkout pages and record why each one is needed. PCI DSS v4.0 requirements 6.4.3 and 11.6.1 require this, along with integrity checks. Use Subresource Integrity hashes for static third-party scripts.
- Enforce a strict Content Security Policy on checkout. Limit
script-srcand, more importantly,connect-srcandform-actionto known domains. That way, injected code cannot easily send card data to an attacker's server. Turn on CSP violation reporting and actually watch the reports. - Monitor what the page actually does in the browser. Server-side file integrity checks will not catch scripts that change only when they reach the visitor's browser. Use synthetic transactions or client-side monitoring to detect new outbound requests or DOM changes on payment forms within hours, not weeks.
- Move card entry off your own page. Use hosted payment fields in iframes served by the payment processor, so card numbers and CVVs never pass through JavaScript your site controls. This greatly reduces what a skimmer can reach.
- Shorten the time from detection to notification. Run card-skimming tabletop exercises that include working with card brands and acquiring banks. A faster compromised-card alert lets issuers reissue cards before the stolen data is used for fraud.
- Warn customers about follow-on phishing. If emails were exposed alongside card data, tell affected customers how you will and will not contact them, and watch for lookalike domains that pretend to offer breach help.
Sources: Fandango says hackers stole payment card details from checkout pages | Fandango breach notice: Which card charges to check Edit USA | Fandango Data Breach: Cards Used Oct. 8–11, 2026 | Fandango Checkout Data Breach: What to Do | Fandango reported a data breach to the CA AG FraudMeNot | Fandango Data Breach: Card Details, What to Do ITD | Fandango’s checkout page leaked card number, CVV, expiry and billin... | Fandango Media, LLC Data Breach Investigation Almeida Law Group