Fandango’s Checkout Was Skimmed for 4 Days. Would Your Team Notice?
Your customers hit Pay, get their receipts, and move on. In those few seconds, a script on your checkout page could send their card details to a criminal. Your dashboard might look normal. How many orders could you process before someone on your team noticed?
What Happened at Fandango
Fandango Media is notifying customers of a breach that exposed payment card details entered on its checkout pages. The company says the exposure occurred from October 8 to 11 and affects customers who purchased through its official website. A card-skimming script injected into the checkout page intercepted payment details as customers placed orders and sent them to the attackers.
The breach notice filed with the California Attorney General lists card numbers, CVVs, expiration dates, billing ZIP codes, and email addresses as potentially exposed. Fandango says it determined on October 30 that individual customers’ information may have been affected. The state lists the reported date as November 13, and customer notifications reportedly began on November 16.
The notice also leaves much unsaid. It doesn’t explain when the issue was first detected, how it was found, or how the unauthorized party reached the checkout page. One analysis notes that the skimmer ran for four days and was discovered through an investigation, not an automated checkout check. That detail is worth dwelling on, because the real risk is how long a skimmer can run before anyone notices.
How Checkout Skimmers Work
Web skimmers, often grouped under the label Magecart, are JavaScript snippets that run in the shopper’s browser. The attacker needs only one way to inject a script into the payment page. Common routes include compromising the site’s CMS or application server, exploiting a vulnerable plugin, using stolen administrator credentials, or compromising a third-party script already loaded on the page. This is background on the attack class, not a finding about how Fandango was compromised.
This is also why shoppers can’t protect themselves. The page looks legitimate, and the order confirmation arrives, while the theft occurs in the background. Third-party dependencies increase exposure. Loading analytics, chat widgets, or advertising libraries from external CDNs creates injection points for skimmers.
What PCI DSS 4.0 Expects
If you accept card payments, two PCI DSS 4.0 requirements address this problem directly. Requirement 6.4.3 requires managing scripts on payment pages: maintaining an inventory, justifying why each is needed, and authorizing it. Requirement 11.6.1 requires a mechanism that detects and alerts on unauthorized changes to payment pages as shoppers’ browsers receive them. Having these controls on paper is not enough. What matters is whether they would actually catch a change within hours rather than days.
Put Your Own Checkout to the Test
Before your next sales campaign, have engineering run a test purchase and record which scripts actually load in the shopper’s browser. Then compare that list with the scripts your team approved. Any script on the first list but not the second needs an explanation.
Then ask your security operations team to walk you through their most recent tamper alert test. What triggered the alert? Who received it? Who would investigate at 2 a.m. on a Saturday? If the answers are vague, you’ve found your gap before an attacker does.
Give third-party scripts the same scrutiny as your own code. A tag used to measure conversions can run on the same page where customers enter their payment details. For each one, ask who owns it and how you would know if it changed.
Practical Steps to Tighten Checkout Security
Start by maintaining a living inventory of every script on your payment pages, with a named owner for each. Remove anything that isn’t essential, since every extra script is another potential entry point. A strict Content Security Policy can limit which sources can run code, and automated change monitoring should alert people instead of relying on manual checks. Finally, ensure alerts reach someone who can act on them outside business hours, because attackers don’t keep office hours.
Don’t Wait for Your Own Breach Notice
One analysis put it bluntly: card skimming is a well-understood attack that occurs mainly where teams don’t closely monitor their own payment pages. Fandango’s four-day window reminds us that real damage can happen quickly. Run the test purchase, check the script list, and ask the uncomfortable questions now.
Discover more from The Digital Guardian
Subscribe to get the latest posts sent to your email.
