Fandango Says Card Numbers, CVVs and Expiry Dates Were Exposed on Its Checkout Page October 8-11. If You Bought Tickets Then, Check Your Statement and Replace the Card

If you bought movie tickets on Fandango between October 8 and October 11, 2026, look at that card's statement for charges you did not make, and ask your bank for a new card number. Fandango Media is notifying customers that payment card details entered on its checkout page in that window may have been exposed: the card number, the security code (CVV), the expiration date, the billing ZIP code and your email address. That is everything a criminal needs to use the card online.
What Fandango says
Per BleepingComputer's report of Monday, November 16, quoting Fandango's customer letter: an unauthorized party could access payment card information associated with certain transactions on Fandango's checkout page from October 8 to 11, 2026. Fandango determined on October 30 that customers' information may have been affected. It says names, government ID numbers and Social Security numbers were not exposed, that it has fixed the issue on its checkout page, that it investigated with outside cybersecurity specialists and that it is not aware of any fraud. It is offering two years of credit and dark web monitoring through IDX; the enrollment deadline is February 13, 2027.
Fandango has not said how many customers were affected or what the cause was. BleepingComputer describes it as skimmer code injected into the checkout page; that is the outlet's description, not words we saw from Fandango. We tried to read Fandango's letter on DocumentCloud and were refused (HTTP 403), so this post rests on BleepingComputer's account of it.
This is not the Optimizely campaign
On Monday we also wrote about a crypto-wallet swapper and card skimmer delivered through Optimizely snippets. Fandango's window, October 8 to 11, ended more than a month before that campaign appeared, Fandango names no vendor, and none of urlscan.io's 12 scans of fandango.com since November 1 loaded Optimizely or the attacker's domain. Two separate incidents, the same lesson: the checkout page runs whatever scripts it is told to load, and the card number is typed into it.
What to do
If you bought on Fandango October 8 to 11: check the statement, dispute anything you do not recognize, and replace the card. Monitoring does not stop a stolen card from being used; a new number does. Watch for phishing emails that use the breach as a reason to "verify" your account; Fandango's letter says your email address was part of what was exposed.
If you run a checkout page: PCI DSS 4.0.1 requirements 6.4.3 and 11.6.1 require an inventory of every script on payment pages, a justification for each, and an alert when the page's scripts or security headers change. A strict Content Security Policy that names the only hosts allowed to load scripts turns an injected skimmer into an error message.
What is not known
How the card data was taken. How many customers. Whether any cards have been used. We published no indicators; none were given.
Sources
BleepingComputer, "Fandango says hackers stole payment card details from checkout pages," November 16, 2026, quoting Fandango Media's customer notification. Fandango's letter on DocumentCloud (document 28911829) could not be retrieved. urlscan.io search for page.domain:fandango.com, November 1 to 16, 2026.
Every indicator in this post is in the feed. Free.
1.58M+ IOCs, STIX 2.1 / TAXII, 88% novel vs ThreatFox, exploited-CVE leads ahead of CISA. No credit card — a free API key in 30 seconds, and you can audit every claim above against the live endpoints.