11.18 million
Burger King Japan (BK Japan) has announced a significant data breach involving the member information system of its official mobile application. Unauthorized third-party access resulted in the exposure of approximately 11.18 million member records. The compromised data includes a wide range of personally identifiable information (PII), creating a substantial risk of phishing and other social engineering attacks against the affected customers. The company has confirmed that financial information was not part of the breach and has notified the relevant Japanese data protection authorities.
The breach occurred due to an unauthorized third party gaining access to Burger King Japan's systems between October 2 and October 7, 2026. The data leak was subsequently confirmed by the company on October 13. The attackers successfully accessed and potentially exfiltrated a database containing detailed information on members of the Burger King mobile app loyalty program. The specific method of access has not been disclosed, but it likely involved an exploited vulnerability in the application's backend infrastructure or compromised credentials.
The investigation into the root cause is ongoing, but the scope of the exposed data has been defined. The breach affected a database containing the following PII for 11.18 million users:
Burger King Japan has stated that it does not store credit card numbers in this system, which significantly mitigates the risk of direct financial fraud. The status of login passwords was not confirmed as leaked, but this remains under investigation. The combination of the other data points, however, is highly valuable for attackers.
While no financial data was lost, the exposure of 11.18 million detailed personal records presents a major security risk. Attackers can use this information to conduct highly convincing and targeted phishing campaigns. For example, an attacker could send an email to a victim that addresses them by their full name and references their date of birth or location, tricking them into revealing more sensitive information like passwords or financial details.
For Burger King Japan, this incident will result in significant reputational damage and loss of customer trust. The company will also face scrutiny from Japan's Personal Information Protection Commission and may be subject to penalties. The cost of incident response, investigation, and customer notification will also be substantial.
No specific technical Indicators of Compromise (IOCs) were provided in the source articles.
There are no specific observables for external parties. Affected individuals should be vigilant for signs of their data being misused.
Detection:
Response:
For Affected Users:
For Organizations:
Hardening the configuration of web servers and databases that support the mobile application to reduce the attack surface.
Enforcing least privilege and strict auditing for accounts that can access the customer PII database.
To prevent breaches of mobile application backends, organizations must prioritize hardening the configuration of all supporting infrastructure. This includes web servers, API gateways, and databases. Security teams should conduct regular configuration reviews against industry benchmarks like the CIS Benchmarks. Key actions for a scenario like the Burger King Japan breach include: ensuring databases containing PII are not publicly accessible, enforcing strong authentication for all administrative interfaces, disabling unnecessary services and ports, and implementing a Web Application Firewall (WAF) to protect against common web-based attacks like SQL injection and cross-site scripting. Furthermore, all API endpoints should have robust authentication and authorization checks to ensure that one user cannot access another user's data (preventing Insecure Direct Object Reference vulnerabilities).
Unauthorized access to Burger King Japan's member information system begins.
The period of unauthorized access ends.
Burger King Japan confirms the data leak.
The company publicly discloses the data breach.

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.
CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.
Help others stay informed about cybersecurity threats
Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.
Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.
Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.
Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.
Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.