Fandango Media, LLC says a security incident involving its ticketing checkout page may have exposed payment card information that shoppers typed when buying tickets on fandango.com during October 8–11, 2026. The South Carolina Attorney General sample letter and matching California AG sample (sb24-632866) state that an unauthorized party could access card data tied to certain transactions on that checkout page, that Fandango determined on October 30, 2026 that your information may have been impacted, and that the company resolved the issue after investigation with outside cybersecurity specialists.
The notice does not describe how access occurred, whether malware was involved, or a nationwide count. BleepingComputer describes card-skimmer code on the checkout page. SecurityWeek says Fandango has not disclosed how the incident occurred. Treat skimming as that outlet’s reporting, not a filed attribution.
We tabulated Fandango in the November 13 California AG week roundup. This post is the standalone consumer steps, retailer takeaway, audit, website-tech, blacklist, lookalike, CourtListener, and MFA write-up for fandango.com.

Snapshot
| Field | Detail |
|---|---|
| Entity | Fandango Media, LLC |
| Checkout site | fandango.com (ticketing purchases on the official website) |
| Exposure window (notice) | Oct 8–11, 2026 (SC sample letter) |
| Impact determination (notice) | Oct 30, 2026 |
| Data categories (notice) | Payment card number, CVV, expiration date, billing ZIP, email address |
| Not involved (notice) | Names, government ID, SSN, other account information |
| Oregon (DOJ table) | 913 individuals · breach 10/8–10/11/2026 · discovered 10/30/2026 · notice sent 11/13/2026 · reported 11/16/2026 |
| Texas (OAG public list) | 6,323 Texans · published 11/17/2026 · consumer notice email |
| Vermont (AG breach notices) | 18 residents · date reported to AGO 11/13/2026 |
| South Carolina (notices index) | 1,205 SC residents · reported 11/13/2026 |
| California (sb24-632866) | Sample posted 11/13/2026 — no public resident count |
| Assistance | 1-866-200-0940 · Mon–Fri 6 a.m.–6 p.m. Pacific, excluding US holidays (per notice) |
| IDX monitoring | 24 months · enroll via the code in your notice at app.idx.us/account-creation/protect · activate by Feb 13, 2027 (per notice) |
What Fandango says was exposed
From the SC sample letter:
- Payment card number, CVV, expiration date, billing ZIP, and email address — for affected checkout transactions in the window above.
- Not first/last name, government ID, SSN, or other account information (per the same notice).
Card data without a name can still fuel card-not-present fraud on other sites, especially when CVV and ZIP traveled with the number.
Attack type — official notice vs reporting
| Source | What it says |
|---|---|
| Fandango sample letter | “Issue involving Fandango’s ticketing checkout page”; unauthorized party could access payment card information for certain transactions Oct 8–11, 2026 |
| BleepingComputer (Nov 2026) | Describes card skimmer code on the checkout page (secondary reporting) |
| SecurityWeek (Nov 2026) | Says Fandango has not disclosed how the incident occurred; does not report skimming. |
Fandango states it is not currently aware of fraudulent use tied to the incident but still urges statement review (SC sample).
Regulatory counts — partial, not a national total
State portals publish jurisdiction-specific numbers. As of November 19, 2026:
| Regulator | Residents / individuals counted | Notes |
|---|---|---|
| South Carolina (notices index) | 1,205 | SC residents · reported 11/13/2026 |
| Oregon DOJ | 913 | Oregon individuals |
| Texas OAG | 6,323 | Texans only |
| Vermont AG | 18 | Vermont residents |
| California AG | — | Publishes sample only |
The California AG index lists a single breach date of October 8, 2026; the sample letter’s transaction window is October 8–11, 2026.
We did not locate a Maine Attorney General listing or a Massachusetts public notice for this incident in searches on November 19, 2026. The consumer letter does not state how many purchasers received notice nationwide.
If you bought Fandango tickets Oct 8–11, 2026
- Review card and bank statements for charges you do not recognize — including small probe charges.
- Dispute unauthorized transactions with your card issuer promptly; ask whether reissuance is appropriate when CVV may have been exposed.
- Type
fandango.comyourself for account or ticket questions — not links from unexpected texts or mail that pressure you to “verify” a card. - If you received a legitimate notice, use only the IDX URL in that letter (
app.idx.us/account-creation/protect) with your unique enrollment code — not a code forwarded from social media. - Prefer a credit card over a debit card, or ideally one low-limit credit card, for future ticket purchases (CISA — Shopping Safely Online).
- Watch for phishing that references “Fandango breach monitoring,” fake IDX pages, or ticket refunds — see email security below.

Small-business takeaway — third-party checkout scripts
E-commerce and ticketing sites often load analytics, tag managers, chat widgets, and payment helpers on checkout. When those scripts change without review, they can become a skimming path — the pattern BleepingComputer describes for Fandango, even though the filed notice does not name a technique.
| Control | Why it matters |
|---|---|
| Content Security Policy (CSP) | Limits which origins can run script on checkout |
| Subresource Integrity (SRI) | The browser can reject a third-party <script src> whose bytes do not match the integrity hash. SRI does not cover inline scripts or tag-manager payloads that change. |
| PCI DSS v4.0.1 §6.4.3 | Authorize each payment-page script, assure its integrity, and keep an inventory with a written reason the script is needed (PCI SSC) |
| PCI DSS v4.0.1 §11.6.1 | Detect and alert on unauthorized changes to payment-page content and to the HTTP headers the browser receives, at least weekly or on the targeted-risk-analysis cadence (PCI SSC) |
| Script inventory + approvals | No “paste this pixel” deployments on checkout without security sign-off |

Merchants should also run a baseline check with the free domain security scan at audit.emailmenow.com (search your apex on the homepage — do not trust emailed ?domain= links). For a written action list after an incident, the Full Audit Report ($99) and ongoing Domain Watch ($29/mo) alerts are described on EmailMeNow services.
Breach-notice phishing and email security
Shoppers may receive fake monitoring, refund, and card-reentry messages. fandango.com scored 35% on identity in our audit — spoofed @fandango.com lures are plausible even when the brand’s website header score is stronger.
| Step | Action |
|---|---|
| 1 | Verify IDX enrollment only through app.idx.us plus a code from your mailed or emailed notice |
| 2 | Never give CVV or full card number in reply to an email or text “confirming” breach assistance |
| 3 | Enforce DMARC reject on domains that send transactional mail for your own business |
| 4 | Run lookalike monitoring when a major retailer publishes a breach sample |

MFA: YubiKey and Google Authenticator (fandango.com accounts)
| Grade | Meaning |
|---|---|
| Fail | SMS, email OTP, phone call, or no published YubiKey / open TOTP |
| Pass | Self-serve Google Authenticator-style open TOTP |
| Strong | FIDO2 / YubiKey-class security key for sign-in |
| N/A | No public login surface on this host |
| Unevaluated | Login exists but MFA docs not public |
| Platform | Grade | YubiKey | Authenticator |
|---|---|---|---|
| Fandango account sign-in (terms §3) | Fail (password-only public) | Not published | Not published |
| Guest checkout (no account) | N/A | N/A | N/A |
Fandango’s Terms of Use describe password-based accounts and password hygiene but do not document FIDO2 or open TOTP enrollment as of November 19, 2026.
Directory: MFA support directory.
Independent cybersecurity audits
EmailMeNow audit run Nov 19, 2026 (read-only admin scan) on fandango.com — no public /?domain= URL and no POST /start. 100% is the ideal overall domain-security score. 0 of 1 scored hosts reach it.
| Organization | Domain | Overall | Gap vs 100% |
|---|---|---|---|
| Fandango (official) | fandango.com | 60% | −40 |
| Domain | Identity | Transport | Website |
|---|---|---|---|
| fandango.com | 35% | 15% | 95% |
How to read this: fandango.com at 60% with 15% transport and 35% identity is mainly a mail authentication / MTA-STS gap — relevant when fake “ticket refund” or “IDX activation” messages spoof the brand. The 95% website pillar reflects HTTPS and header checks on the marketing hosts we probed; HSTS is present; the CSP header does not restrict script sources — it does not prove checkout script integrity during October 2026.
These scores measure public email authentication, transport policy, and website headers. They do not prove whether card data was copied in the Oct 8–11 window.

Website stack
Passive website-tech probe on November 19, 2026; live headers re-checked November 19, 2026 with curl -sI:
| Signal | Detail |
|---|---|
| Edge | Akamai (Server: AkamaiGHost on fandango.com → www.fandango.com) |
TLS (live, www.fandango.com) | DigiCert · CN www.fandango.com · expires 2027-03-04 (handshake) |
| TLS (CT, crt.sh) | Amazon RSA 2048 M01 · *.fandango.com · expires 2027-04-02 |
| HTTP → HTTPS | http://fandango.com 301 → http://www.fandango.com/; http://www.fandango.com 302 → https://www.fandango.com/; https://fandango.com 301 → https://www.fandango.com/ (live curl -sI, Nov 19, 2026) |
| Response headers | HSTS is present; the CSP header is upgrade-insecure-requests; block-all-mixed-content only — it does not restrict script sources. X-Frame-Options: SAMEORIGIN on www.fandango.com. |
| Fingerprint | Platform undetected (low confidence) — common on large CDNs |
| security.txt | Not found (RFC 9116) |
Point-in-time only — edge headers on the marketing hosts are not a live PCI ASV attestation of checkout JavaScript.
Blacklist and lookalikes
Email blacklist (public DoH, November 19, 2026): fandango.com clear (0 mail/domain hits on checked lists).
DNS lookalike scans on fandango.com (BEC profile, 162 string variants checked):
| Profile | To review | BEC staging | Note |
|---|---|---|---|
| BEC | 81 | 0 | 21 strings HTTP-redirect toward www.fandango.com (likely defensive registrations) |
| Examples | — | — | fandang.com, fndango.com, candango.com — unrelated live sites possible |
Registered lookalikes with MX without an obvious brand redirect deserve extra scrutiny during breach-mail season, even when BEC staging reads zero. Continuous monitoring: Cybersquat Domain Monitoring.
CourtListener
CourtListener REST search on November 19, 2026 for “Fandango” plus data breach returned no federal docket naming Fandango Media, LLC tied to the November 2026 state AG samples. Re-check before assuming litigation status unchanged.
Related coverage
- California AG breaches — week of Nov 13, 2026
- Breach data week — Nov 15, 2026
- Hospitality & retail breach tracker
- State AG breach reports hub
Sources: SC AG sample letter · SC breach notices index · California AG sb24-632866 · Oregon DOJ Data Breach list · Texas OAG Data Security Breach Reports · Vermont AG breach notices · BleepingComputer · SecurityWeek. Independent EmailMeNow audit, website-tech, blacklist, cybersquat, and CourtListener work November 19, 2026.