Fandango warns of October checkout payment card exposure | Magica
Fandango warns checkout incident may have exposed card numbers and security codes
Editorial Team
••📖5 min read
Fandango says payment details from certain October 8–11 transactions may have been exposed. State disclosures provide only a partial affected count, while the company has not explained how the checkout page was compromised.
Fandango says certain October 8–11, 2026, checkout transactions may have exposed card numbers, security codes and other payment details.
The nationwide affected count and technical cause remain undisclosed; reports differ in how firmly they describe data theft.
Customers are being offered two years of identity-protection services, with enrollment due February 13, 2027.
Fandango Media, the US online movie-ticket seller, is notifying customers that an unauthorized party could access payment information associated with certain checkout transactions. Its notice describes possible exposure of card numbers and CVV security codes even though names and other account information were not involved.
Magica timeline based on Fandango’s customer notice and Oregon’s breach filing. Events appear in chronological order; spacing does not represent elapsed time. Source: California Department of Justice.
What the checkout notice establishes
Fandango says in its customer notice filed in California that the affected transactions occurred from October 8 through October 11, 2026. On October 30, it determined that recipients’ information may have been affected.
The potentially exposed information includes payment card numbers, CVVs, expiration dates, billing ZIP codes and email addresses. Fandango says first and last names, government-issued identification information, Social Security numbers and other account information were not involved. The exposed combination could enable unauthorized online purchases, a report on the incident explains.
That report describes injected card-skimming code intercepting checkout information and sending it to attackers. Fandango’s notice does not identify malicious code or confirm that data was taken: it says investigators found evidence that an unauthorized party could access the information. A separate account of the disclosures says the company has not disclosed how the incident occurred. The public notice therefore does not substantiate the more specific account of skimming and theft.
The management company supporting Japan's Shonan Beauty Clinic network disclosed stolen customer passwords stored without encryption and a separate booking-service incident. Treatment-related submissions were also exposed, while the affected population and financial impact remain under investigation.
Editorial Team
Fandango says it investigated with outside cybersecurity specialists, resolved the issue and strengthened its processes and protections. It has not specified those changes. The company also says it is not currently aware of fraudulent use resulting from the incident; that is not confirmation that no misuse occurred.
State filings give only a partial count
Fandango, a Versant Media Group brand that also operates the Rotten Tomatoes review site, handles ticket sales for more than 31,000 US movie screens, according to the report on state disclosures. That reach describes its ticketing business, rather than the number of customers exposed during the four-day transaction window.
The Oregon Department of Justice’s breach database lists 913 people affected in Fandango’s filing, identified as Oregon residents in the reporting on state disclosures. It records October 30 as the discovery date, November 13 as the date notices were sent and November 16 as the report date. Fandango’s own notice describes October 30 more narrowly as the date it determined recipients’ information may have been affected, without specifying when it first detected the checkout issue.
The Oregon database cautions that its public figures reflect initial reports and are not updated for supplemental notices. The same report on state filings also identifies 18 affected Vermont residents and a California submission, which is required when notices go to more than 500 California residents. These disclosures do not establish a nationwide total, which Fandango has not released.
Magica chart using state-filing counts reported by SecurityWeek: 913 Oregon residents and 18 Vermont residents. These disclosures do not establish a nationwide total. Source: SecurityWeek.
An earlier case brought long-term security requirements
Fandango’s security record includes a 2014 settlement with the Federal Trade Commission, the federal consumer-protection agency. In its announcement of the proposed settlement, the FTC alleged that Fandango disabled SSL certificate validation in its iOS app from March 2009 until February 2013 despite promising secure handling of payment information.
The disabled check left app communications vulnerable to interception, according to the FTC. The information at risk included card details, email addresses and passwords. The agency also alleged inadequate basic security testing and a deficient process for receiving vulnerability reports.
The FTC approved final settlement orders in August 2014. The terms required a comprehensive security program addressing risks in application development and independent security assessments every other year for 20 years, alongside a prohibition on misrepresenting product and service privacy or security.
Those requirements give the earlier case significance beyond a past vulnerability. But it concerned mobile-app transmission security, and the current notice concerns checkout-page access. The public disclosures do not establish a shared cause or a violation of the FTC order.
Customer deadlines and the evidence still needed
Fandango advises customers to review financial accounts and credit reports and promptly report unauthorized transactions to their card issuer or bank.
Its notice offers affected customers 24 months of free IDX identity-protection services, including single-bureau credit monitoring, dark-web monitoring and managed identity-theft recovery. Customers must activate the services by February 13, 2027, using the enrollment instructions in their notice. The package includes reimbursement insurance of up to $1 million for expenses associated with restoring an identity, subject to policy terms, limits and exclusions.
The unresolved questions are how the checkout page became accessible, whether payment information was actually taken, and how many customers were affected nationwide. A technical explanation of the incident and the protections added would also allow a clearer assessment of Fandango’s response than its general assurance that the issue has been fixed.
N-able says an intruder reached a server supporting Mail Assure and SpamExperts Hosted Cloud. Mail delivery and filtering continued, but customers lost management access as the company revoked tokens and worked to restore services securely.
Microsoft is testing an optional Edge mode that blocks WebGL and WebGPU to reduce opportunities for browser exploitation. An early hands-on test found that restoring graphics for a trusted site also removed its broader Enhanced Security protections.
A critical authentication bypass gave a suspected China-linked espionage group access to VMware's virtualization control plane. Mandiant says the campaign stole signing keys and virtual-machine data, making compromise checks essential alongside patching.
PHP’s November 19 security releases address seven critical flaws, including unauthenticated code execution through reused backend connections. Patching takes priority, but applications that retain session upload progress must also check shared storage and serialization settings.
TfL has shut its Oyster photocard website after a breach that may have exposed around 265,000 customers’ account details, including security answers. Existing cards still work, while the attack method and restoration timetable remain undisclosed.
Around 40 Irish credit unions are implicated in a saved-payee data breach at software supplier Wellington IT. Missing logs leave the victim count unresolved, while a minister is seeking answers about the disclosure delay.
JPMorganChase says it believes attackers accessed marketing data at outside service providers, potentially exposing customer names and email addresses. The bank says services are unaffected, but has not identified the vendors or disclosed the attack date.
Apache confirms exploitation of a Roller code-execution flaw that survives disabling XML-RPC in its administration panel. Attacks on the retired Axis 1.x library also expose enterprise applications, making product-specific mitigation and compromise checks urgent.
StepSecurity’s Elephant-led Series A will fund broader protection for developer machines, package downloads and build pipelines, alongside planned defenses for AI-agent sandboxes. Its challenge is turning open-source adoption into a larger commercial platform while proving the extra controls earn their place.
Nvidia says it has found no indication its own systems were affected after The Gentlemen ransomware group listed it on a leak site. The investigation concerns a possible incident at a partner, while the gang has supplied no public proof.
Senators from both parties plan to delay the CISA nomination of Palantir security chief Michael LoSapio after his Jan. 6 denial, adding a confirmation obstacle as the agency faces staffing losses and funding decisions.
Sean Cairncross is leaving as national cyber director, with Pentagon CIO Kirsten A. Davies reportedly selected to succeed him. The transition puts Senate confirmation at the center of a cybersecurity leadership reshuffle.
Windows baseline protection combines existing PC safeguards into a verifiable pass-or-fail result. Microsoft defines the standard; developers choose whether failure means a warning, fewer features or blocked access.
F5 lists fixed releases for a critical nginx HTTP/2 flaw, while the wider NGINX2Root disclosure covers five independent nginx attack paths and a separate Linux kernel bug. Remediation depends on configuration, supplier patch levels and replacing vulnerable running processes.
Tyler Robert Buchanan received six years in U.S. prison for a phishing and SIM-swapping conspiracy that stole at least $11.6 million from individuals. He is the last of five defendants sentenced; restitution remains pending.
The new Threat Disruption Center makes TRM Labs its main technology partner following a reported $94.66 million sole-source award for Homeland Security Task Force investigations. A rival lost its court challenge, but the launch leaves the center’s share of that spending and its performance benchmarks undisclosed.
Norway’s state-controlled oil and gas group is working to neutralise an attack on some IT systems. Employee services may be disrupted, but Equinor says operations and production remain unaffected and it has found no indications of data theft.
Tor urges relay operators to install 0.4.9.17 as a continuing DDoS attack strains its privacy network. A post-upgrade operator account describes further disruption, while Bitcoin connectivity measurements show partial recovery with important limits.
Malicious code in Optimizely website-testing projects could swap cryptocurrency addresses and skim payment cards. Optimizely says it has fixed the vulnerability and removed the code, but visitor exposure and losses remain unquantified.