Fandango card breach: bought movie tickets online October 8–11? Check your statement
Someone got at card details typed into Fandango's checkout page over four days in October. If you bought tickets then, a quick look at your card statement is the main job.
Developing story · Fandango's checkout card breachAction neededCheck your card if you bought on Fandango Oct 8–11- Fandango says an outsider could get at card details entered on its checkout page for some orders between October 8 and 11, 20261,4.
- Exposed: card number, security code (CVV), expiry date, billing ZIP code and email address. Fandango says names and Social Security numbers weren't involved1,4.
- Fandango says it fixed the page and knows of no fraud so far. It hasn't said how many people are affected3,4.
- Bought tickets those days? Check your statement and report odd charges3. We'd also get a new card and use the free monitoring in Fandango's letter1.
Should you care?
3/5 Check your card if you bought tickets Oct 8–11
How hot right now
HotSecurity outlets covered it November 16–18; no total customer count yet
Fire meter checked Nov 19, 2026
Hype check
We'll check back on Feb 17, 2027: did it live up to the hype?
Who is this for?
- ✓People who bought Fandango tickets online Oct 8–11, 2026For youThose are the dates Fandango gives for the problem on its checkout page1.
- ✓Anyone who got a letter or email from Fandango about thisFor youYour card details may have been seen, and the letter has a code for two years of free identity protection1,4.
- ✕Fandango customers who bought on other datesSkip itFandango's notice covers only orders from October 8 to 111.
- ✕People who paid at a theater box officeSkip itThe incident Fandango describes was on its online ticket checkout page1.
- ~People who run online shops or checkout pagesMaybeIt's a reminder that card rules now require tracking every script on a payment page7.
Bought movie tickets on Fandango October 8–11? Here's what to do
For four days in October, someone could see card details people typed into Fandango's checkout page. If you bought tickets between October 8 and 11, check your card statement and talk to your bank.
Fandango, the website for buying movie tickets, is telling some customers that their payment card details may have been stolen1,3. For four days, from October 8 to 11, 2026, an outsider could get at card information typed into Fandango's checkout page for some orders1,4.
Think of it like someone quietly reading over your shoulder while you type your card details into the website. Paying worked as normal, but a copy went somewhere it shouldn't.
What may have been seen
Your card number, the three- or four-digit security code (usually on the back), the expiry date, your billing ZIP code and the email address you used1,4. Fandango says names, Social Security numbers and ID documents were not involved4.
What Fandango has done
Fandango says it fixed the problem, brought in outside security experts, and doesn't know of anyone using the stolen details for fraud so far1,4. On October 30 it worked out which customers may be affected, and it is now writing to them1,3. It hasn't said how many people that is4.
What to do
If you didn't buy tickets on Fandango during those four days, you can relax. This doesn't touch you1.
If you did, don't panic. Look through your card statement for anything you don't recognize, and report it to your card company3. Because the security code was exposed too, our advice is to ask your bank for a new card number. Once you have it, the old details are useless to a thief.
If you got a letter from Fandango, it includes a code for two years of free identity protectionJargon busterA service that watches for signs someone is using your personal details, like new accounts opened in your name.. You have until February 13, 2027 to sign up1,4.
One more thing: scammers love news like this. If an email or text about the breach asks you to click a link or "confirm" your card, don't. To talk to your bank, use its app or the phone number on the back of your card.
What should you do?
What Fandango confirmed, what it didn't, and what to watch
Fandango's notice confirms the data and the dates but not the method. BleepingComputer and The Record describe malicious code planted on the checkout page.
What the notice says, and what it skips
Fandango's letter, filed with California's attorney general on November 13, is short on detail1,2. It points to a problem with its ticket checkout page and says someone without permission was able to reach card data from some transactions1. It does not say how the attacker got in or how the data was taken4,5.
The "skimmer" description comes from BleepingComputer, which reported that malicious code planted on the checkout page grabbed card details as people placed orders and sent them to the attackers3. Fandango's own letter doesn't name a technique1,4. The Record, writing about a separate incident, also said hackers had planted malicious code in Fandango's checkout page6. The data list fits that picture: a CVVJargon busterThe three- or four-digit security code on your card that online shops ask for to check you have the card. is typed fresh at checkout and shouldn't be stored afterwards, so taking it at the moment of typing is the obvious route10.
Why this is worse than an email leak
Most breaches we cover leak emails or login details. This one leaked a working card: number, expiry, CVV and billing ZIP1. That's the full set many online shops check, so it's ready to use for online shopping fraud. The good news is that a card is easy to replace. Once your bank issues a new number, the stolen one is worthless.
The response, rated
Fandango is offering 24 months of free IDX identity protectionJargon busterA service that watches for signs someone is using your personal details, like new accounts opened in your name.1,4. That's the standard offer, but it fits this breach poorly: identity monitoring watches for new accounts opened in your name, while the real risk here is charges on an existing card. A replacement card does more good. It's still worth enrolling, since your email was also exposed.
Four days is a short window, which is good news. How Fandango spotted the problem so fast is something its letter doesn't say.
What to watch
Fandango still hasn't given a total. State filings only show local slices: Vermont's attorney general lists 18 Vermont residents in Fandango's November 13 notice11, and SecurityWeek reported filings listing 913 in Oregon4. So watch for the total number of people affected, whether Fandango explains how the code got onto its page, and whether lawsuits follow. The same week, website-tools company Optimizely confirmed that attackers had used its platform to slip harmful code onto some customers' sites. The Record compared that with the Fandango case6, but we found no report connecting the two.
By the numbers
How we got here
- Oct 8, 2026Exposure window on Fandango's checkout page begins1
- Oct 11, 2026Exposure window ends1
- Oct 30, 2026Fandango identifies affected customers1,3
- Nov 13, 2026Notice filed with California's attorney general2
- Nov 16, 2026BleepingComputer reports the breach3
- Feb 13, 2027 · coming upLast day to enroll in free IDX protection1
Client-side skimming, why the CVV gives it away, and PCI DSS 4.0's script rules
The data set points to capture in the browser, not a database dump. PCI DSSJargon busterThe security rulebook card companies require every business that takes card payments to follow. 4.0.1 has required script inventories and tamper detection on payment pages since March 31, 2025.
Timeline (per Fandango and filings)
| Date | Event |
|---|---|
| Oct 8–11, 2026 | Exposure window on the checkout page1 |
| Oct 30, 2026 | Affected customers identified1,3 |
| Nov 13, 2026 | Notice filed with the California AG2; Vermont's AG lists one dated the same day11 |
| Feb 13, 2027 | IDX enrollment deadline1 |
Why the CVV points to the browser
PCI DSSJargon busterThe security rulebook card companies require every business that takes card payments to follow. Requirement 3.3.1 bans storing sensitive authentication data, which includes the card verification code, after authorization, even encrypted10. A compliant merchant shouldn't have CVVs at rest, so a database dump shouldn't yield them. Data captured in transit, at the form, would. That's consistent with BleepingComputer's skimmer account3, though Fandango hasn't confirmed a vector4. A server-side compromise of the checkout backend before authorization would also fit, so treat the method as open.
How web skimming works
The usual pattern is a small piece of JavaScriptJargon busterThe programming language websites use to run code inside your browser., either injected directly into the payment page or loaded via a tampered third-party script. It hooks form fields or the submit event, serializes the card fields, and beacons them to an attacker-controlled host, while the real payment completes normally. The 2018 British Airways case is the textbook example: the ICO's penalty notice describes cardholder data being sent from britishairways.com to the lookalike domain BAways.com9.
PCI DSS 4.0's answer
Two requirements target this attack, and both became mandatory on March 31, 20257:
| Requirement | What it demands |
|---|---|
| 6.4.3 | Inventory every script on the payment page, justify it in writing, authorize it and assure its integrity7 |
| 11.6.1 | Detect and alert on unauthorized changes to scripts and security-impacting HTTP headers as the browser receives them7 |
In practice that means Content Security PolicyJargon busterA website setting that tells the browser which sources of code the page is allowed to load and talk to., Subresource IntegrityJargon busterA fingerprint attached to an outside script so the browser refuses to run it if it has been changed. hashes on static third-party scripts, and some form of monitoring of what the page actually runs. Merchants that fully outsource payment to an iframeJargon busterA window inside a web page that shows content from another website, often used for payment forms. and validate with SAQ AJargon busterA short PCI self-assessment form for shops that hand the whole payment form to a payment provider. had 6.4.3 and 11.6.1 replaced by an eligibility check: they must confirm their site isn't susceptible to script attacks, either with similar techniques or via their processor8. The Council stresses the underlying requirements weren't weakened8.
We don't know how Fandango's checkout is built, which SAQ it validates against, or whether these controls were in place. A four-day window is consistent with change detection doing its job, but Fandango hasn't said how it found the problem.
Open questions
- Was the payload first-party or delivered through a third-party script?
- Were app purchases affected, or only the web checkout?
- How did the attacker get write access to the page?
- What is the total count? It will surface as more state filings land.
The facts
Hover or tap anything underlined to see what it means.
- Company
- Fandango Media, LLC2
- What was hit
- Fandango's online ticketing checkout page1
- Exposure window
- October 8–11, 20261
- Reported to California AG
- November 13, 20262
- Data exposed
- Card number, CVVJargon busterThe three- or four-digit security code on your card that online shops ask for to check you have the card., expiry date, billing ZIP, email1,4
- Not involved
- Names, Social Security numbers, government IDs4
- Offered
- 24 months of free IDX identity protectionJargon busterA service that watches for signs someone is using your personal details, like new accounts opened in your name.1,4
- Enroll by
- February 13, 20271
- Status
- Checkout page fixed, outside specialists brought in1
Jargon buster
- Data breach
- When someone gets into a company's systems without permission and sees or copies customer information.
- CVV
- The three- or four-digit security code on your card that online shops ask for to check you have the card.
- Card skimmer
- Anything that secretly copies card details as you use your card; online, it's hidden code on a payment page.
- Web skimming
- Stealing card details by planting code on a website's checkout page that copies what shoppers type.
- Magecart
- A nickname for web-skimming attacks, from early groups that targeted online shops built on Magento.
- JavaScript
- The programming language websites use to run code inside your browser.
- Identity protection
- A service that watches for signs someone is using your personal details, like new accounts opened in your name.
- PCI DSS
- The security rulebook card companies require every business that takes card payments to follow.
- SAQ A
- A short PCI self-assessment form for shops that hand the whole payment form to a payment provider.
- Content Security Policy
- A website setting that tells the browser which sources of code the page is allowed to load and talk to.
- Subresource Integrity
- A fingerprint attached to an outside script so the browser refuses to run it if it has been changed.
- Iframe
- A window inside a web page that shows content from another website, often used for payment forms.
Fandango's checkout card breach
Card details typed into Fandango's checkout in October were stolen. How many people were hit, and what comes next.
- Oct 8, 2026Card details typed into Fandango's checkout start being captured (until October 11) California Attorney General
- Nov 13, 2026Fandango files its breach notice with California's attorney general California Attorney General
- Nov 19, 2026What Fandango customers from October 8–11 should do You're reading this
- Feb 13, 2027 · coming upLast day to sign up for Fandango's free identity protection California Attorney General
- How many customers were affected (state breach filings)
- How the attackers got into the checkout page
- Reports of fraud using the stolen cards, or lawsuits
Sources11 pages · California Attorney General, BleepingComputer, SecurityWeek and moreShowHide
The small numbers in the text point to these pages. Everything is written in our own words. How we work · Spotted a mistake? Tell us
- 1Fandango individual notice template (redacted sample letter) · California Attorney General
- 2Search Data Security Breaches (Fandango Media, LLC entry) · California Attorney General
- 3Fandango says hackers stole payment card details from checkout pages · BleepingComputer
- 4Fandango Warns Ticket Buyers of Payment Card Data Exposure · SecurityWeek
- 5Fandango Data Breach Puts Card Numbers and CVVs at Risk, Filing Shows · eSecurity Planet
- 6Website management platform Optimizely confirms hackers put malicious code into customer sites · The Record
- 7New Information Supplement: Payment Page Security and Preventing E-Skimming · PCI Security Standards Council
- 8Important Updates Announced for Merchants Validating to Self-Assessment Questionnaire A · PCI Security Standards Council
- 9British Airways penalty notice (October 2020) · UK Information Commissioner's Office
- 10FAQ: Can sensitive authentication data be stored before authorization? · PCI Security Standards Council
- 11Security Breach Notices (Fandango Media, LLC entry, November 13, 2026) · Vermont Attorney General
Read next
Security & privacy · ★ Saved
Capcom ID breach exposes 11.7 million records: what was taken and what to do
Hackers saw email addresses and login details from about 11.7 million Capcom player account records. Your card is safe, but be very careful with emails that claim to be from Capcom.
Security & privacy · ★ Saved
Microsoft's November update fixes an Outlook bug hackers are already using
Microsoft fixed a bug in the classic Outlook email app for Windows that criminals are already using. Run Windows Update, then update Office separately.
Money & business · ★ Saved
Anthropic, maker of Claude, prices its stock market debut at $83 a share, above its range
Anthropic, maker of the Claude chatbot, set the price for its first public share sale at $83, above the $70 to $78 it had pencilled in. Trading on the Nasdaq exchange is expected to start Thursday.