Fandango · Breach

Fandango confirms card skimmer stole payment details from checkout

· 1 min read

Fandango confirmed that a skimmer injected into its website checkout page captured full card numbers, CVVs, expiration dates, billing ZIP codes, and email addresses for purchases made between October 8 and 11, 2026. The company has fixed the page, says it is unaware of any fraud using the data, and is offering two years of credit and dark web monitoring, with enrollment open until February 13, 2027. Customers who bought tickets in the window should monitor statements and report unauthorized charges to card issuers.

WhatsApp LinkedIn X
HighBreachNo software to update

In 30 seconds

DarkWebInformer
Observed

Fandango, the movie ticketing platform, has confirmed a data breach and says hackers reached payment details entered on its checkout pages between October 8 and 11, 2026. According to the disclosure, the exposed information potentially includes full card numbers, CVV security codes, expiration dates, billing ZIP codes and email addresses. The company says the issue is resolved, reports no known cases of fraud so far, and is offering affected customers two years of free credit monitoring and identity protection. BleepingComputer reported the story on November 16, 2026.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listbleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source list

What happened

Alleged

Fandango's account of the incident, as relayed in the reporting, is that attackers gained access to payment information while customers typed it into the checkout pages during a window from October 8 to 11, 2026. The capture happened at the moment of purchase. Authorship and method remain the company's attribution; nothing in this evidence batch independently confirms how the intruders got in or exactly what they took.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listbleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source list

Observed

The notification itself is on the record. It lists the at risk fields as potentially full card numbers, CVV codes, expiration dates, billing ZIP codes and email addresses, and pairs the bad news with remedies: the issue has been resolved, there are no known fraud cases so far, and two years of free credit monitoring and identity protection are on offer. One number is missing from the record: how many customers were affected.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list

Why it matters

Inferred

The presence of CVV codes is the detail that tells the story. Merchants are not supposed to store those codes after a transaction, so their appearance in the exposed set implies the data was read as it was being typed, the signature of a checkout page interception rather than a stolen card database. For customers, that means a complete kit for fraudulent transactions may be in someone else's hands: card number, verification code, expiry date and billing ZIP. The disclosure itself flags that risk.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list

What to do

Inferred

If you bought movie tickets on Fandango around October 8 to 11, 2026, check your card statements for charges you do not recognize and call your bank about anything odd; a replacement card neutralizes a compromised number. Enrolling in the two years of free credit monitoring and identity protection Fandango is offering is a reasonable step, since email addresses and billing ZIP codes may also be exposed. No fraud has been reported so far, per the company, but watching costs nothing.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list

Confirmed and still uncertain

Observed

Established so far: Fandango has confirmed the breach, the exposure window ran October 8 to 11, 2026, the at risk data fields are enumerated, and a customer remedy package exists. Still unknown: the number of affected customers, which remains undisclosed, and the root cause. The available material says nothing about how the attackers entered or what fix sits behind the word resolved.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listbleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source list

Alleged

Two load bearing claims rest on the company's word alone: that the issue has been resolved, and that no fraud cases are known so far. These come from the party that was breached, and the batch holds no independent verification of either. Treat them as the current company line, subject to revision as banks and customers report back.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list

What people are saying

Observed

BleepingComputer broke the story on November 16, 2026 and pushed it to its X audience with a straight headline: Fandango says hackers stole payment card details from checkout pages.bleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source listBleepinComputerx.com · BleepinComputer · xOpen original sourceSee in source list

Observed

DarkWebInformer, an account that tracks breach disclosures, amplified the story about two and a half hours later with the granular version: the October 8 to 11 window, the full field list including CVV codes, the credit monitoring offer and the undisclosed customer count. The same account explicitly credits BleepingComputer as its source, so the richer detail flows from the same reporting chain, not an independent one.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list

Evolution

Observed

The story arrived in two steps on one day. BleepingComputer's report came first, on November 16, 2026, framing the incident as card details stolen from checkout pages. DarkWebInformer's follow up, roughly two and a half hours later, gave it boundaries: a four day exposure window in October, a specific list of exposed fields, a company that calls the issue resolved, and an open question about scale. The narrative moved from a headline to a bounded incident, with the caveats and the missing headcount now visible.bleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list

Reach

Observed

2 independent groups, 2 updates, and 10 engagements.

Technical detail

Inferred

The technical picture fits a checkout page intercept: payment details captured at the moment customers entered them. The field list supports that reading, because CVV security codes are not meant to be kept after a purchase, so their exposure implies the data was grabbed at input time, behavior consistent with digital skimming attacks that plant malicious code on payment pages. What the batch lacks is any technical indicator: no sample of the malicious code, no description of the entry vector, no forensic detail. Those specifics, if they surface, would let independent researchers verify the company's account rather than take it on faith.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listbleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source list

Sources and evidence

Observed

The evidence base is small and single sourced at its root. It consists of one BleepingComputer article, promoted by the outlet's own X account, plus a detailed summary from DarkWebInformer that explicitly points back to BleepingComputer as its source. Every factual detail in this item traces to Fandango's disclosure as relayed through that one chain.bleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source listBleepinComputerx.com · BleepinComputer · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list

Observed

A limitation worth naming: the article's body was not available in this batch, only its headline and links, so the granular facts here rest on DarkWebInformer's summary of the company's disclosure. That is a company statement relayed twice, not independent verification. The summary post carries a screenshot credited to DarkWebInformer, which is the visual in circulation. Regulator filings or the notification letter itself would firm up the timeline and the field list if they surface.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list

Sources

  1. DarkWebInformerx.com · DarkWebInformer · x
  2. bleepingcomputer.combleepingcomputer.com · rss
  3. BleepinComputerx.com · BleepinComputer · x
  4. DarkWebInformerx.com · DarkWebInformer · x

Incidents like this, every morning

The ones that need action first, in a 3-minute read.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Get the next one tomorrow morning

One email a day with what changed, what to fix first and how.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click

Share it with your team

Whoever handles security with you should get it too.

LinkedIn X

Your colleague gets a confirmation request. Nothing is sent unless they confirm.

See all news

Read also

Before you go: get this every day

The HIFY Radar daily edition lands every morning with the incidents that need action. Free.

Free · 1 email a day, in the morning · no spam, unsubscribe in 1 click